beam-commits mailing list archives

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


Davor Bonaci commented on BEAM-148:

Ha! (Thanks Dan.)

It turns out this is a long-standing issue. The build wouldn't have passed for 'mvn verify'
in the Dataflow codebase either, if it wasn't for released artifacts in Maven Central. Basically,
the build for 'mvn verify' always used archetypes from HEAD and either previously released
SDK from Maven Central, or something manually built in the local repository. It *never* used
an artifact built in the context of this Maven build invocation.

This is now exposed because we have no releases with these Maven coordinates.

Great -- issue understood.

> 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