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

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-19598:
------------------------------------

Until we adopt the buildchow stuff (feel free to start on that if you're comfortable "breaking" all the master jobs) we're still using the git backup of jenkins config w/ the sync mojo.

Once we move to buildchow I think it's still a good idea to periodically save a snapshot of what's on the server into github, so we can more easily track things. When we're satisfied that buildchow handles all the jobs and all the permutations (including _master and _4.3.mars/_9.0.mars streams) we can drop that step and just rely on the generator templates.

Sound good?

> 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
>             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)