[jbosstools-issues] [JBoss JIRA] (JBIDE-19598) Use "Build other project (extended)" to cascade aggregation

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-19598:
----------------------------------------

It's actually the Downstream-ext-plugin https://wiki.jenkins-ci.org/display/JENKINS/Downstream-Ext+Plugin .
The composite install job is there to trigger aggregate in case of change. If we have the "Build other project (extended)" plugin, then we can directly trigger aggregate in case of SCM change, instead of using the intermediary composite-install (which is used in order to create a diff between 2 successive installs and decide whether to aggregate or not).

> Use "Build other project (extended)" to cascade aggregation
> -----------------------------------------------------------
>
>                 Key: JBIDE-19598
>                 URL: https://issues.jboss.org/browse/JBIDE-19598
>             Project: Tools (JBoss Tools)
>          Issue Type: Enhancement
>          Components: build
>    Affects Versions: 4.3.0.Alpha2
>            Reporter: Mickael Istria
>            Assignee: Mickael Istria
>            Priority: Minor
>             Fix For: 4.3.0.Beta2
>
>
> In order to decide whether to cascade aggregation when components are build, we could use the "Build other project (extended)" plugin in order to trigger 2 aggregate jobs (site, coretests-site) when component has SCM changes.
> This would require changing all 17 component jobs (per stream = 34 jobs), but would eliminate the need for the composite-install test jobs [1].
> [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-install_master/



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)