[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:comment-tabpanel&focusedCommentId=12755251#comment-12755251 ] 

Nick Boldt edited comment on JBIDE-13600 at 2/19/13 10:04 PM:
--------------------------------------------------------------

New script to install and display the contents of the installation footprint:

https://raw.github.com/jbosstools/jbosstools-build-ci/master/util/installAndDisplayCompositeSiteContent.sh

Three jobs which detect if the composite staging site has changed, verify its contents can be installed via p2.director, and will cause the JBT aggregate / JBDS product builds to fire:

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-install_master/
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-install_41/
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-install_40/

Side effect is that these manifests are now produced:

http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trunk/composite.site.IUs.txt
http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.1.kepler/composite.site.IUs.txt
http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.0.juno/composite.site.IUs.txt
                
      was (Author: nickboldt):
    Three jobs which detect if the composite staging site has changed, verify its contents can be installed via p2.director, and will cause the JBT aggregate / JBDS product builds to fire:

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-install_master/
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-install_41/
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-install_40/

Side effect is that these manifests are produced too:

http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trunk/composite.site.IUs.txt
http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.1.kepler/composite.site.IUs.txt
http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.0.juno/composite.site.IUs.txt
                  
> 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
>
> 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