beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Halperin (JIRA)" <>
Subject [jira] [Commented] (BEAM-148) Jenkins build failure on start project
Date Thu, 24 Mar 2016 05:52:25 GMT


Daniel Halperin commented on BEAM-148:

And pointing out that the test that failed on Jenkins and in `mvn verify` did in fact execute
and pass when run on `mvn install`.

> Jenkins build failure on start project
> --------------------------------------
>                 Key: BEAM-148
>                 URL:
>             Project: Beam
>          Issue Type: Bug
>          Components: testing
>            Reporter: Daniel Halperin
>            Assignee: Davor Bonaci
> FYI [~jasonkuster].
> See -- 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

View raw message