Properly escape variables in Jenkinsfile - #282
Merged
datho7561 merged 1 commit intoMay 11, 2026
Merged
Conversation
This will mean the declared bash variables get used instead of trying to substitute Jenkins variables into the string before running. Signed-off-by: David Thompson <davthomp@redhat.com>
datho7561
force-pushed
the
properly-escape-in-jenkinsfile-this-time
branch
from
May 11, 2026 13:55
571e3ce to
d1ea439
Compare
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
1 participant
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 will mean the declared bash variables get used instead of trying to substitute Jenkins variables into the string before running.