[
https://issues.jboss.org/browse/JBTM-1645?page=com.atlassian.jira.plugin....
]
Michael Musgrove edited comment on JBTM-1645 at 12/1/13 10:15 AM:
------------------------------------------------------------------
At least QA_JTA does not work since qa/run-tests.xml is missing the ci-tests-nojts
target.
Note that I did not check whether any of the other targets might be missing too so that
needs to be investigated.
My comment applies to the 4.17 branch only
If you don't need JTA QA testing then a partial workaroud is to configure the PR with
!QA_JTA
was (Author: mmusgrov):
At least !QA_JTA does not work since qa/run-tests.xml is missing the corresponding
target.
Note that I did not check whether any of the other targets might be missing too so that
needs to be looked as well.
My comment applies to the 4.17 branch only
Allow pull requests to configure some parameters in
scripts/hudson/narayana.sh
------------------------------------------------------------------------------
Key: JBTM-1645
URL:
https://issues.jboss.org/browse/JBTM-1645
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Build System
Reporter: Tom Jenkinson
Assignee: Gytis Trikleris
Fix For: 5.0.0.M5, 4.17.17
Original Estimate: 4 hours
Time Spent: 1 hour, 40 minutes
Remaining Estimate: 0 minutes
If the pull description has something like this:
export NARAYANA_BUILD=1 AS_BUILD=1 NARAYANA_TESTS=1 TXF_TESTS=1 XTS_TESTS=1
XTS_AS_TESTS=1 txbridge=1 QA_TESTS=1 [SUN_ORB=0] [JAC_ORB=1] [QA_TARGET=ci-jts-tests]
We could use it in scripts/hudson/narayana.sh if we detect it is a pull build. We might
need to white list users we apply this to.
--
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