[
https://issues.jboss.org/browse/JBIDE-10964?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-10964:
------------------------------------
It's mostly s/trunk/stable_branch/g or s/trunk/branches\/jbosstools-3.3.0.Beta3/g or
s/trunk/branches\/devstudio-5.0.0.Beta3/g, but there are exceptions to that rule, too. For
example, when both stable and trunk are building against the same TP jobs, or pulling from
the same Drools upstream. Also, there's no template job for stable, only for trunk.
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