[JENKINS-75512] Ensure SIGPIPE is not hidden when calling shell script to avoid hanging. #253
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.
This change aims at fixing the hanging issue we hit when using a JDK 21 agent image to run Jenkins and some
sh
command that require SIGPIPE to work fine in order to finish. See the example of such a command in the ticket JENKINS-75512 (https://issues.jenkins.io/browse/JENKINS-75512) as well as explanations.Here we wrap the call to
nohup
by a call toenv --default-signal=SIGPIPE
to avoid this issue. Since not all Linux distro will supportenv --default-signal=SIGPIPE
(this flag was introduced in 2019 in coreutils), wrap this in some more complex shell command to be able to fallback to not usingenv
at all if the OS doesn't support it.Testing done
The details of the testing done is in the ticket JENKINS-75512 (https://issues.jenkins.io/browse/JENKINS-75512) (checked via commands run inside a fedora container).
Submitter checklist