Adding restoration of the keychains as a build wrapper #31
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.
New approach to keychain restoration. I did not consider aborting a build manually in my first pull request. After a bit of research I found that a
BuildWrapper
should be the appropriate extension point for restoring the keychains, because it will be run even if the user aborts the build manually.It may be set in the global configuration which keychains are to be restored. See screenshots attached. The switch for the "Restore keychain" field is because of an annoying bug(?). I had checkboxes first, but when checking just a few keychains to be restored, the ones which are not, won't get saved. See https://groups.google.com/forum/?fromgroups#!topic/jenkinsci-dev/PAf3mFWv1LI