Jenkins Pipeline Updates#2815
Conversation
…ccount running agents for EMC global-workflows
…ccount running agents for EMC global-workflows
…n the Jenkins Controller
Co-authored-by: David Huber <69919478+DavidHuber-NOAA@users.noreply.github.com>
|
Experiment C48_S2SW FAILED on Hercules in Build# 26 in |
|
Experiment C48_ATM FAILED on Hercules in Build# 26 in |
|
Experiment C48_S2SWA_gefs FAILED on Hercules in Build# 26 in |
|
Experiment C96C48_hybatmDA FAILED on Hercules in Build# 26 in |
|
Experiment C96_atm3DVar FAILED on Hercules in Build# 26 in |
|
CI Failed on Hercules in Build# 26 |
|
Experiment C48_ATM FAILED on Hercules in Build# 29 in |
|
Experiment C48_S2SW FAILED on Hercules in Build# 29 in |
|
Experiment C96C48_hybatmDA FAILED on Hercules in Build# 29 in |
|
Experiment C96_atm3DVar FAILED on Hercules in Build# 29 in |
|
CI Failed on Hercules in Build# 29 |
|
CI Passed on Hercules in Build# 30 |
Description
Pipeline updates:
ghlocation on remote machine and define global bash env variable$GHfor GitHub CLINOTE: failFast (quitting all cases on failing of one) still does not work because it isn't quitting the running remote shells. We can make this a configurable capability in feature request with some custom code. The current behavior has the remaining cases continuing to run after a FAIL label has been issued and it is incumbent of the code manager to kill the CI job in the controller before resetting another Ready label.
Type of change
How has this been tested?
Ran in the authoritative repo with full self-tests