[jbosstools-issues] [JBoss JIRA] (JBIDE-13307) Set up the "All JBoss Tools" build+test

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-13307:
------------------------------------

6 new flows set up:

{code}
(1) Base
 \-> (2) Forge|Freemarker|GWT (parallel)
 \-> (3) Server>(webtools.aggregate|WS|OS) (server first, rest in parallel)
 \-> (4) (Hibernate>BIRT)|(Xulrunner>VPE>JST) (two parallel series of builds)
      \-> (5) JavaEE>Portlet>Central (series)
           \-> (6) JBT.aggregate>(JBT.tests|JBDS)
{code}

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow.1_master/
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow.2_master/
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow.3_master/
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow.4_master/
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow.5_master/
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-buildflow.6_master/

Flow.1 is configured to run some time on Sat or Sun between midnight and 9am. The rest should cascade down in sequence.

Results / progress can be seen from this view:

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk_Pipeline/


                
> Set up the "All JBoss Tools" build+test
> ---------------------------------------
>
>                 Key: JBIDE-13307
>                 URL: https://issues.jboss.org/browse/JBIDE-13307
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: Build/Releng
>            Reporter: Mickael Istria
>            Assignee: Nick Boldt
>             Fix For: 4.1.0.Alpha1
>
>
> This job would take all JBoss Tools and build everything at once. It can be used to ensure everything builds together.

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