[jbosstools-issues] [JBoss JIRA] (JBIDE-13600) new mechanism for deciding automatically if JBT & JBDS aggregate jobs should fire

[Nick Boldt (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-13600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt resolved JBIDE-13600.
--------------------------------

    Fix Version/s: 4.0.1.Final
                   4.1.0.Alpha1
                   4.1.0.Alpha2
       Resolution: Done


Working. 
                
> new mechanism for deciding automatically if JBT & JBDS aggregate jobs should fire
> ---------------------------------------------------------------------------------
>
>                 Key: JBIDE-13600
>                 URL: https://issues.jboss.org/browse/JBIDE-13600
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Build/Releng, updatesite
>    Affects Versions: 4.0.1.Final, 4.1.0.Alpha1, 4.1.0.Alpha2
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 4.0.1.Final, 4.1.0.Alpha1, 4.1.0.Alpha2
>
>
> We need a series of jobs for 4.0.x, 4.1.x, and master which will:
> * install a comma-separated list of IUs (.feature.groups) from a composite site into a pre-existing Eclipse installation, then 
> * diff whether the fresh installation differs from a previously cached install manifest (list of features/plugins)
> * if the install footprint is different from before, the composite site contains new content and we should fire a downstream job to produce a new aggregate site

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