Update Dockerfile to cope with Persistent Storage deployment on Origin or elsewhere. #49
Conversation
This file contains 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
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.
In aim to keep the Jenkins jobs & history, we need to keep the jenkins_home persistent.
Here the Dockerfile modified is making a copy of the original jenkins_home in a reference place, and it adds the copy from this ref to the original place, if this one is detected empty when the start.sh is run (start of the container)
I have validated this on my own instances (3 clusters)
I have also the updated CD-Pipeline to get the PVC.
This change is backward compatibile and work well if the attachment is not done.
JMarc