[jbosstools-issues] [JBoss JIRA] (JBIDE-12514) Do not have jobs blocked by upstream

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-12514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714883#comment-12714883 ] 

Nick Boldt commented on JBIDE-12514:
------------------------------------

+1 for components, especially under the new github reorg strategy (JBIDE-12475).

But what about for aggregate builds? should they wait until all their upstream are done? Or spin with the possibility that there's a dependency chain breakage somewhere, eg., that the latest AS depends on a different version of WTP than Openshift, and therefore p2 won't let the two be installed concurrently. 

By waiting until all the components are done churning, we ensure that everyone's built with each other, and so the aggregate should be more cohesive than if we just grab "whatever's available at that time." But that could also mean it takes DAYS for a clean spin of the aggregates, if all the upstream are constantly churning.

Maybe the midground solution here is to always build the aggregates from integration builds instead of nightly?
                
> Do not have jobs blocked by upstream
> ------------------------------------
>
>                 Key: JBIDE-12514
>                 URL: https://issues.jboss.org/browse/JBIDE-12514
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: Build/Releng
>            Reporter: Mickael Istria
>            Assignee: Nick Boldt
>
> Currently, when a component is building, all components relying on it are blocked and have to wait for this one to finish before running. If another of their deps is waiting and builds before, it waits over and over again.
> We should disable this lock so builds can perform in parallel. It may cause some failure because of sync from times to times, but we'll probably save hours of wait for feedback.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira