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

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-19598:
---------------------------------------------

what plugin is it exactly ? 

And buildchow has "raw" support now so even if it does not support it natively we can add the raw xml for it until that happens.

About save snapshot of what is on the server in github to easily track things that seems wrong to me. 
The easy way to track things are to have the changes recorded in buildchow and then if we wanted (for backup reasons)
to commit the generated config.xml files. We should stop taking any configs from the server and commit - only reason to take from server is to try find what the diff is in case of some error.

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