Launch Multiple Platforms to Jenkins with polling#2548
Conversation
|
Experiment C48_S2SWA_gefs FAILED on Hercules with error logs: Follow link here to view the contents of the above file(s): (link) |
|
Experiment C48_S2SWA_gefs FAILED on Hercules in |
|
Automated global-workflow Testing Results: |
|
Experiment C96C48_hybatmDA FAILED on Hercules with error logs: Follow link here to view the contents of the above file(s): (link) |
|
Experiment C96_atm3DVar FAILED on Hercules in |
|
Experiment C96C48_hybatmDA FAILED on Hercules in |
|
Experiment C48_ATM_19605adc SUCCESS on Wcoss2 at 04/29/24 04:06:13 PM |
|
Experiment C48_ATM FAILED on Orion with error logs: Follow link here to view the contents of the above file(s): (link) |
|
Experiment C48_ATM FAILED on Orion in |
|
Experiment C96C48_hybatmDA FAILED on Orion with error logs: Follow link here to view the contents of the above file(s): (link) |
|
Experiment C96C48_hybatmDA FAILED on Orion in |
|
Experiment C96_atm3DVar_19605adc SUCCESS on Wcoss2 at 04/29/24 05:12:17 PM |
|
Experiment C96C48_hybatmDA_19605adc SUCCESS on Wcoss2 at 04/29/24 05:12:28 PM |
|
Experiment C48_S2SW_19605adc SUCCESS on Wcoss2 at 04/29/24 05:18:10 PM |
|
All CI Test Cases Passed on Wcoss2: |
|
CI Passed Hera at |
|
Seem like this PR is successfully doing what it set out to do and any remaining issues on MSU machines are unrelated. |
|
Experiment C48_S2SW FAILED on Hercules with error logs: Follow link here to view the contents of the above file(s): (link) |
|
Experiment C48_S2SW FAILED on Hercules in |
|
Experiment C96_atm3DVar FAILED on Orion in |
Description
When launching Jenkins CI Tests all requested RDHPCS machines can now be selected via the Ready label at once.
This is all that is required sense polling also works now on the controller end.
Killing the jobs still needs to be done directly on the Jenkins Controller.
Do not try to update the CI process using Labels. It is for launching only.
Jenkins will update the labels as the states change.
NOTE: When a case fails the label will be update to a Fail for that system but will continue to report failures of subsequent cases until otherwise stopped in the Jenkins Controller directly.
Do not update any labels to Ready until a push has been made to the repo of the PR, and
The job has been completed or stopped directly on the controller first.
You can do this at anytime without having to wait until the other machines are completed.
Type of change
Change characteristics
How has this been tested?
This PR will be self tested by running Jenkins on it with three labels at once