Capture build fail in Jenkins pipeline when no error logs are produced #3297
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…duce an error log file in the logs dir
TerrenceMcGuinness-NOAA
added
bug
TerrenceMcGuinness-NOAA
requested a review
from WalterKolczynski-NOAA
as a code owner
DavidHuber-NOAA
approved these changes
Feb 4, 2025
WalterKolczynski-NOAA
approved these changes
Feb 4, 2025
|
Rats, just missed the merge for the uptick for the gdas build though |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The catch block for a build fail in the Jenkins pipeline did not capture the case when there are no error logs produced.
This is has been rectified with this update. The compute build shell script still could be enhanced by creating a
error.logfile in the log directory.Resolves #3296
Type of change