[JENKINS-34073] Revert fix for JENKINS-21486 #2236
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
|
This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation. |
| this.version = osgiProperties[0]; | ||
| } else { | ||
| this.version = version; | ||
| } |
There was a problem hiding this comment.
Note that this part was actually a bug fix, and should be safe to keep. But yeah it can be reinstated later.
|
Sigh, 🐝 |
|
🐝 |
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.
This reverts #2072 and #2228.
That change caused the perceived regression predicted in #2001 (comment) before it even landed in a release.
Details in the issue: https://issues.jenkins-ci.org/browse/JENKINS-34073
Temporarily backing out of it for 2.0 RC. A proper solution, that includes UI, towards 2.1 would be welcome.
@reviewbybees
CC @fbelzunc @Vlatombe (Sorry!)