[
https://issues.jboss.org/browse/JBTM-2568?page=com.atlassian.jira.plugin....
]
Michael Musgrove commented on JBTM-2568:
----------------------------------------
I updated narayana.sh to read any name=value pairs from the pull description and set them
as environment variables in the job. In addition, a pair of the form PROFILE=xyz where xyz
is one of our standard job axes (QA_JTS_JDKORB, QA_JTA, XTS, MAIN, BLACKTIE, PERF) will
just run that single axis for the PR. For example the PR description:
bq. PROFILE=QA_JTS_JDKORB QA_PROFILE=-Dprofile=hornetq QA_TESTGROUP=crashrecovery02_2
QA_TESTMETHODS=CrashRecovery02_2_Test31 NARAYANA_TESTS=0
will result in just the QA_JTS_JDKORB axis being run (PROFILE=QA_JTS_JDKORB) using the
journal store (QA_PROFILE=-Dprofile=hornetq). The QA_TESTGROUP and QA_TESTMETHODS
environment variable settings will result in just a single method being tested.
Add config options to enable fine grained control of what's
tested in a PR
--------------------------------------------------------------------------
Key: JBTM-2568
URL:
https://issues.jboss.org/browse/JBTM-2568
Project: JBoss Transaction Manager
Issue Type: Feature Request
Components: Testing
Affects Versions: 5.2.8.Final
Reporter: Michael Musgrove
Assignee: Michael Musgrove
Priority: Optional
Fix For: 5.next
Currently we have a fixed set of Jenkins CI config profiles when testing PRs
(QA_JTS_JDKORB, QA_JTA, XTS, MAIN, BLACKTIE and PERF) and we are allowed to selectively
disable one or more of them.
It would be handy to be able to control other things such as running QA tests using the
journal store (which none of the above QA profiles allow). It would also be a handy
shortcut to explicitly set which profile to run (as opposed to which ones to disable).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)