[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=12762814#comment-12762814 ] 

Nick Boldt edited comment on JBIDE-13307 at 3/24/13 4:09 PM:
-------------------------------------------------------------

Builds 9 and 10 were also blue, now that we're ignoring failures just to ensure everything builds on the weekend (and if anything is new, it will publish the changes).

However, it should be noted that the time to run a full stack varies from under 6hrs to 18hrs!

{code}
#9	7 hr 53 min	dev05-rhel5-x86_64
#8	18 hr	dev05-rhel5-x86_64
#5, #6, and #7 all failed
#4	5 hr 21 min	dev05-rhel5-x86_64
{code}

We could still move to the other approach of "all sources in one workspace, then build it all at once" but for now I'm satisfied w/ the output we get for the BuildFlow job. 

!http://snag.gy/GY019.jpg!
                
      was (Author: nickboldt):
    Builds 9 and 10 were also blue, now that we're ignoring failures just to ensure everything builds on the weekend (and if anything is new, it will publish the changes).

However, it should be noted that the time to run a full stack varies from under 6hrs to 18hrs!

{code}
#9	7 hr 53 min	dev05-rhel5-x86_64
#8	18 hr	dev05-rhel5-x86_64
#5, #6, and #7 all failed
#4	5 hr 21 min	dev05-rhel5-x86_64
{code}
                  
> 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.Alpha2
>
>
> 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