-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Jenkins Pipeline Updates #2815
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 <[email protected]>
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
|
…e_rocoto * origin/develop: Jenkins Pipeline Updates (NOAA-EMC#2815) Add Gaea C5 to CI (NOAA-EMC#2814) Add support for forecast-only runs on AWS (NOAA-EMC#2711) Add fixes to products for when REPLAY IC's are used (NOAA-EMC#2755) Add capability to run forecast in segments (NOAA-EMC#2795)
Pipeline updates: - get `gh` location on remote machine and define global bash env variable `$GH` for GitHub CLI - Failed cases are now displayed accordingly in the Jenkins dashboard (see NOTE below) - Added the Build # in messaging for clarity when running from re-runs. - Replaced Matrix construct for concurrency with the parallel method that can use dynamic case lists - With removing of the hard coded list of cases we now get list of cases dynamically from the PR case directory - See new look of dashboard below (has more annotations and displays only used cases) NOTE: **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. --------- Co-authored-by: David Huber <[email protected]>
Description
Pipeline updates:
gh
location on remote machine and define global bash env variable$GH
for 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