-
Notifications
You must be signed in to change notification settings - Fork 166
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
0e7c803
commit f4c0bb9
Showing
9 changed files
with
402 additions
and
78 deletions.
There are no files selected for viewing
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 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 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 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 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 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
Oops, something went wrong.
f4c0bb9
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This commit is causing PCT failures in
command-launcher-plugin
:@yaroslavafenkin @dwnusbaum Can you please restore compatibility or else adapt
command-launcher-plugin
to this breaking change and release a new version for PCT?f4c0bb9
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here's a PR with the fix: jenkinsci/command-launcher-plugin#47
f4c0bb9
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also breaks
jp.ikedam.jenkins.plugins.extensible_choice_parameter.SystemGroovyChoiceListProviderJenkinsTest#testConfiguration{1,2}
as noticed in jenkinsci/extensible-choice-parameter-plugin#59.f4c0bb9
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also breaks
EnvInjectEvaluatedGroovyScriptTest#testWorkaroundSecurity86
as observed in jenkinsci/envinject-plugin#268.@yaroslavafenkin @dwnusbaum Is there a plan to file PRs to adapt these tests?
f4c0bb9
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, but if the maintainers are having trouble understanding how to adapt their tests and/or plugin code, I am happy to provide feedback in a PR.
f4c0bb9
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not? As far as I can tell, this is a regression caused by this commit.
f4c0bb9
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The security team makes a best effort to maintain compatibility when making fixes, and to fix significant regressions caused by security fixes, especially in critical ecosystem plugins, and in less popular plugins when the issue is raised around the time the original fix is made or if the maintainer asks for help, but we do not and have not ever committed to fixing all security fix-induced regressions in all plugins in the ecosystem regardless of when the issue is raised.
f4c0bb9
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I fail to see the relevance of when the issue is raised. This change caused a previously passing test to start failing, so the authors of this change ought to fix the breakage, regardless of when the issue is raised.