Clean up Jenkins log#452
Merged
evaneschneider merged 17 commits intocholla-hydro:devfrom Nov 21, 2025
Merged
Conversation
As I understand it, the Jenkins `sh` step (for executing shell scripts) sets the interpretter based on the presences of a shebang. When no shebang is present, it defaults to using the system default shell with the `-xe` flag. For the uninitiated, * `-x` enables tracing mode * `-e` tells the script to exit on errors The reference page can be found here: https://www.jenkins.io/doc/pipeline/steps/workflow-durable-task-step/#sh-shell-script Ordinarily, setting the `-x` flag is a really nice choice. But, because the shell configuration script does so much work on the CRC cluster, it ends up polluting the logs. Consequently, this commit tries to specify a shebang to launch the shell shell scripts without enabling tracing mode.
mabruzzo
changed the title
Collaborator
|
Should this be closed now that #449 is merged? |
Collaborator
Author
|
Uh, this is doing something slightly different. This is trying to reduce the amount of "garbage" printed in the log. I need to take another look at this (and resolve all of the newly created conflicts) |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
As I understand it, the Jenkins
shstep (for executing shell scripts) sets the interpretter based on the presences of a shebang. When no shebang is present, it defaults to using the system default shell with the-xeflag. For the uninitiated,-xenables tracing mode-etells the script to exit on errorsThe reference page can be found here:
https://www.jenkins.io/doc/pipeline/steps/workflow-durable-task-step/#sh-shell-script
Ordinarily, setting the
-xflag is a really nice choice. But, because the shell configuration script does so much work on the CRC cluster, it ends up polluting the logs.Consequently, this commit tries to specify a shebang to launch the shell shell scripts without enabling tracing mode.