[jbosstools-issues] [JBoss JIRA] (JBIDE-10964) use "-Dmaven.test.failure.ignore=true" in component jobs to make test failures appear yellow instead of red
Mickael Istria (JIRA)
jira-events at lists.jboss.org
Fri Apr 6 04:44:48 EDT 2012
[ https://issues.jboss.org/browse/JBIDE-10964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682299#comment-12682299 ]
Mickael Istria commented on JBIDE-10964:
----------------------------------------
Beta3 branch is branched from code, isn't it? So shouldn't we branch beta3 jobs from trunk jobs too?
> use "-Dmaven.test.failure.ignore=true" in component jobs to make test failures appear yellow instead of red
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-10964
> URL: https://issues.jboss.org/browse/JBIDE-10964
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 3.3.0.Beta1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 3.3.0.Beta3
>
>
> We'd like to see "unstable" (yellow) when tests fail, not "failed" (red).
> This will also mean checking for missing TEXT-*.xml files (recursing through ${WORKSPACE}/sources/tests/ looking for plugins' target/ folders to see that every test plugin has at least 1 TEST-*.xml file) and generating empty ones should there be an eclipse crash before a test results file can be generated. An empty file should at least alert developers that there's a possible problem w/ their test (or more likely, it's a slave / vnc issue, like JBIDE-10960).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list