[jbosstools-issues] [JBoss JIRA] (JBIDE-12946) add code coverage support to jbosstools-4.0_trunk.tests; make job yellow when tests fail, not red

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-12946:
----------------------------------------

[~dgolovin]: Your opinion is highly welcome: what should we do with this job
# Keep it as it (successive tests)
# Build everything in one maven exec
# Build+Test everything in one Maven exec
# Build all incrementally (using "mvn install" to resolve deps instead of relying on sites)
# Remove it and forget it.
# ...

I think option 2 is the only one that adds value to all the stuff we already have, since it ensure we can build stuff in an autonomous way (useful if we need to rebuild JBT in 10 years).
                
> add code coverage support to jbosstools-4.0_trunk.tests; make job yellow when tests fail, not red
> -------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-12946
>                 URL: https://issues.jboss.org/browse/JBIDE-12946
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: Build/Releng, testing
>    Affects Versions: 4.0.0.Beta2
>            Reporter: Nick Boldt
>            Assignee: Mickael Istria
>             Fix For: 4.0.0.CR2
>
>
> Need your help here. 
> I've migrated https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-4.0_trunk.tests/ to use 15 git repos and run a mvn build 7 times (2 x bootstrap builds for central and birt, then 5 x single component builds).
> But I'm getting this error:
> {code}
> [WARNING] The requested profile "coverage" could not be activated because it does not exist.
> [WARNING] The requested profile "local.requirements" could not be activated because it does not exist.
> {code}
> Can you work your magic to enable code coverage for this job?
> Also, can you enable the "test failures are yellow, not red" stuff you did for the other component jobs? That way we can get results for ALL the mvn runs when hibernate's tests fail, rather than the job crapping out on the first failed test.

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