Enable multiple replay script overrides via Jenkins CLI#227
Open
sic-bre wants to merge 2 commits intojenkinsci:masterfrom
Open
Enable multiple replay script overrides via Jenkins CLI#227sic-bre wants to merge 2 commits intojenkinsci:masterfrom
sic-bre wants to merge 2 commits intojenkinsci:masterfrom
Conversation
…rball with multiple script files to override at once
sic-bre
force-pushed
the
feature-tar-script-override
branch
2 times, most recently
from
f5621f5 to
7339e93
Compare
sic-bre
force-pushed
the
feature-tar-script-override
branch
from
7339e93 to
0af21cf
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 is an extension of the -s flag in replay-pipeline for Jenkins CLI.
I've added a new flag (-S) that accepts a tarball of scripts, which override multiple scripts at once. This allows me (and others, hopefully) to develop complex pipeline scripts locally, and test the scripts against a development instance of Jenkins before committing them to source control.
I suspect there are some things to clean up, and I'm happy to do so, if I could get a review.
Using this looks like:
Thanks