[JENKINS-69905] Backport SECURITY-2824 for Jenkins 2.332.x users #622
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-69905 and 1af77ff. Because
script-security
only requires Jenkins 2.332.1, users running Jenkins 2.332.x who installscript-security
andworkflow-cps
from the plugin manager will end up with incompatible versions (script-security
will have the SECURITY-2824 fix, butworkflow-cps
will not). There is not currently an easy way to directly control the version ofscript-security
offered to 2.332.x users (so that we could offer them the most recent version without the SECURITY-2824 fix), so instead we decided to just backport the SECURITY-2824 changes to the last version ofworkflow-cps
that supports 2.332.x.In retrospect, we should have bumped the minimum supported Jenkins version in
script-security
to 2.346.1 as part of the fix for SECURITY-2824 to avoid this kind of issue.