Attempt to record some of the Jenkins CI setup#99
Merged
Conversation
big-r81
reviewed
Mar 11, 2026
big-r81
reviewed
Mar 11, 2026
big-r81
reviewed
Mar 11, 2026
Contributor
Author
Thank you, Ronny |
We had a recent case where on Jenkins upgrade our CI broke and it took a while to figure it out how to restore it from scratch (missing plugins, wiped configuration settings, etc). This is an attempt to record some of the configuration in a repo to next time it could be used as a reference (diff against jenkins.yaml, or just retrace steps manually).
nickva
force-pushed
the
jenkins-setup-backup
branch
from
319ed7b to
ea3cef5
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
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.
We had a recent case where on Jenkins upgrade our CI broke and it took a while to figure it out how to restore it from scratch (missing plugins, wiped configuration settings, etc).
This is an attempt to record some of the configuration in a repo to next time it could be used as a reference (diff against jenkins.yaml, or just retrace steps manually).