[
https://issues.jboss.org/browse/JBIDE-10964?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-10964:
----------------------------------------
Trust me, I've tried all approaches here and the current one is
the least effort.
Ok, I'll trust you and apply changes to stable_branch as well.
About job linkage, isn't it just about replacing "trunk" by
"stable_branch" in config.xml (except for SVN path) ?
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