Framework: Parameterize CDash Tracks for Pull Request Tests
Created by: william76
@trilinos/framework We discussed parameterizing the PR testing drivers so we can specify in the Jenkins job which track we'd like the tests to go to.
I'm testing this on my fork, but I added a parameter PULLREQUEST_CDASH_TRACK
which, if set and non-empty will set the CDASH_TRACK
variable that's used inside the PullRequestLinuxDriver-Test.sh
script.
I'm running a quick test using my jenkins simulator and it looks like it's working as intended... using '0000' as the PR number, it's showing up in the Clean track here.
Tasks
-
Update PullRequestLinuxDriver-Test.sh
to take in a parameter for the desired CDash track to report results to. -
Add parameter PULLREQUEST_CDASH_TRACK
to Trilinos_pullrequest_cuda_9.2 -
Add parameter PULLREQUEST_CDASH_TRACK
to Trilinos_pullrequest_gcc_4.8.4 -
Add parameter PULLREQUEST_CDASH_TRACK
to Trilinos_pullrequest_gcc_4.9.3 -
Add parameter PULLREQUEST_CDASH_TRACK
to Trilinos_pullrequest_gcc_4.9.3_SERIAL -
Add parameter PULLREQUEST_CDASH_TRACK
to Trilinos_pullrequest_gcc_7.2.0 -
Add parameter PULLREQUEST_CDASH_TRACK
to Trilinos_pullrequest_gcc_7.3.0 -
Add parameter PULLREQUEST_CDASH_TRACK
to Trilinos_pullrequest_intel_17.0.1 -
Update PR Driver configuration in the autotester.
FYI: @jwillenbring