You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Davor Bonaci (JIRA)" <ji...@apache.org> on 2016/06/26 07:09:33 UTC

[jira] [Resolved] (BEAM-148) Jenkins build failure on start project

     [ https://issues.apache.org/jira/browse/BEAM-148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Davor Bonaci resolved BEAM-148.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 0.1.0-incubating

> 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
>             Fix For: 0.1.0-incubating
>
>
> 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)