[jbosstools-issues] [JBoss JIRA] Issue Comment Edited: (JBIDE-9219) Split up continuous and test builds for SOA/JBDS split

[Nick Boldt (JIRA)]

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

Nick Boldt edited comment on JBIDE-9219 at 8/24/11 1:09 PM:
------------------------------------------------------------

Have created 2 new root poms:

pom-core.xml (23 components):

vpe, jst, jsf, forge, seam
cdi, jmx, archives, as, hibernate
freemarker, struts, ws, portlet, examples
birt, maven, deltacloud, gwt, common
runtime, usage, xulrunner

pom-soa-tooling.xml (12 components):

esb, jst, common, tests, smooks,
jbpm, flow, bpel, archives, jmx
modeshape, usage

New/edited trunk jobs are:

http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.continuous/
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.soa-tooling.continuous/

https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.tests/
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.soa-tooling.tests/

Plus this jobs which are currently disabled pending code freeze for M3:

http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.continuous/
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.soa-tooling.continuous/

http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.tests/
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.soa-tooling.tests/

Currently, blocked by these test failures:

{code}
[INFO] org.jboss.tools.smooks.ui.bot.test ................ FAILURE [1.645s] - JBIDE-9460
[INFO] org.jboss.tools.esb.validator.test ................ FAILURE [55.80s] - JBIDE-9582
[INFO] org.jboss.tools.jbpm.ui.bot.test .................. FAILURE [0.742s] - JBIDE-9469
{code}

      was (Author: nickboldt):
    Have created 2 new root poms:

pom-core.xml (23 components):

vpe, jst, jsf, forge, seam
cdi, jmx, archives, as, hibernate
freemarker, struts, ws, portlet, examples
birt, maven, deltacloud, gwt, common
runtime, usage, xulrunner

pom-soa-tooling.xml (12 components):

esb, jst, common, tests, smooks,
jbpm, flow, bpel, archives, jmx
modeshape, usage

New/edited trunk jobs are:

http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.continuous/
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.soa-tooling.continuous/

https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.tests/
https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.soa-tooling.tests/

Plus this jobs which are currently disabled pending code freeze for M3:

http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.continuous/
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.soa-tooling.continuous/

http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.tests/
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.soa-tooling.tests/

Currently, blocked by these test failures:

{code}
[INFO] org.jboss.tools.smooks.ui.bot.test ................ FAILURE [1.645s] (https://issues.jboss.org/browse/JBIDE-9460)
[INFO] org.jboss.tools.esb.validator.test ................ FAILURE [55.800s]
[INFO] org.jboss.tools.jbpm.ui.bot.test .................. FAILURE [0.742s] (https://issues.jboss.org/browse/JBIDE-9469)
{code}
  
> Split up continuous and test builds for SOA/JBDS split
> ------------------------------------------------------
>
>                 Key: JBIDE-9219
>                 URL: https://issues.jboss.org/browse/JBIDE-9219
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: bpel, bpm, drools, esb, jbpm, modeshape, pi4soa, Savara, smooks, teiid
>    Affects Versions: 3.3.0.M1
>            Reporter: Brian Fitzpatrick
>            Assignee: Nick Boldt
>             Fix For: 3.3.0.M3
>
>
> This arose in an e-mail from Nick: 
> "Should we be splitting the cont's and test builds apart so they don't include the SOA components in the Core builds?
> Realize that I split up the aggregate + JBDS update site builds, but not the all-in-one tests job or the "does everything compile?" jobs."
> I think the answer is "yes" we need to do these things. The upside is that it should speed up the component builds on both sides of the equation. The downside is that it means more work for Nick and/or Doug. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira