[jira] [Closed] (INFRA-7034) sling-trunk-oak build runs a larger build when started downstream

["Gavin (JIRA)" <ji...@apache.org>]

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

Gavin closed INFRA-7034.
------------------------

       Resolution: Fixed
    Fix Version/s: February 2014

Please re-open if you find time to test and this doesnt work. (The builds look good to me now.)

> 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
>             Fix For: February 2014
>
>
> 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
(v6.1.5#6160)