[JENKINS-62231] Warn about downgrade issue #462
Merged
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
|
I've added release notes for the security releases with this warning included. since this file is for older releases people might not think to look in here. We can included it in both WDYT? |
res0nance
approved these changes
May 11, 2020
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.
See JENKINS-62231
I've created this PR to warn users about the problem downgrading from any of the security releases. The issue triggers you loose your cloud configuration.
The workaround is to remove the ec2.xml file before restarting Jenkins. This file is created if you click on the button Dismiss these messages of the new AdministrativeMonitor which warns you when you have templates with a weak template. If you don't do that, there isn't any issue.
I was pondering to put this kind of warning in the
index.jellyfile, to have it very visible when you see the update on the pluginManager. Because here, is very late IMO.