[
https://issues.apache.org/jira/browse/BEAM-148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15209779#comment-15209779
]
Daniel Halperin commented on BEAM-148:
--------------------------------------
Is there a way to version the Jenkins config with the tests? We're really
completely unable to keep the tests and configuration green together without it.
> Jenkins build failure on start project
> --------------------------------------
>
> Key: BEAM-148
> URL: https://issues.apache.org/jira/browse/BEAM-148
> Project: Beam
> Issue Type: Bug
> Components: testing
> Reporter: Daniel Halperin
> Assignee: Davor Bonaci
>
> FYI [~jasonkuster].
> See https://github.com/apache/incubator-beam/pull/72 -- the travis build runs
> all phases and passes, but the jenkins build fails in artifact resolution for
> the starter project. I suspect this is related to one of these:
> * Travis uses `mvn install` while Jenkins uses `mvn clean verify`. Maybe one
> populates the catalog differently, and the old build was only not failing
> because we have google-cloud-dataflow artifacts in Maven central.
> * Jenkins and Travis differ on maven version and have issues related to the
> `-incubating` tag we added.
> Or something else.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
