www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gavin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-7034) sling-trunk-oak build runs a larger build when started downstream
Date Mon, 06 Jan 2014 08:13:50 GMT

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

Gavin updated INFRA-7034:

    Status: Waiting for user  (was: Waiting for Infra)

please try once more from a commit to the upstream sling/trunk build. 
I've told the dependent build to use the launchpad/testing dir for the mvn command, meaning
it should use the correct pom file.

If that does not work, then we can look at reverting to per commit for both builds if necessary.

> sling-trunk-oak build runs a larger build when started downstream
> -----------------------------------------------------------------
>                 Key: INFRA-7034
>                 URL: https://issues.apache.org/jira/browse/INFRA-7034
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Buildbot
>            Reporter: Bertrand Delacretaz
>            Priority: Minor
> According to the sling.conf file the sling-trunk-oak build should just build sling/trunk/launchpad/testing
but if started automatically after the upstream sling-trunk build runs, it builds the full
sling trunk instead.
> If it makes things simpler, starting the sling-trunk-oak build on any commit is fine
as well.
> This build was started manually and is ok:
> http://ci.apache.org/builders/sling-trunk-oak/builds/5
> (compile stdio starts at "Building Apache Sling Launchpad Testing")
> Whereas this one was started downstream and wrongly builds everything:
> http://ci.apache.org/builders/sling-trunk-oak/builds/6
> (compile stdio says "Reactor Build Order" and the whole list of projects, and duration
is 21 minutes vs 2-3 minutes)

This message was sent by Atlassian JIRA

View raw message