-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
-
680.v3a_6a_1698b_864
When upgrading from version 670.vc71a_a_c00039e to 675.va_5f27678f6d6, the role-strategy plugin is now saying that it is dependent on the authorize-project plugin. I believe this is unintentional.
When support was added for accessing user roles in a pipeline (PR#324), it looks like the test scope of the authorize-project dependency was accidentally removed, so it's now considered to be compile scope.
See commit a5f27678f6d61a330597b9b157ca7468158835f5
As far as I can see, the only place the org.jenkinsci.plugins.authorizeproject classes are used is in the test code.
[JENKINS-71772] Role-based Authorization Strategy has unnecessary dependence on Authorize Project plugin
Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
Assignee | Original: Oleg Nenashev [ oleg_nenashev ] | New: Mark Waite [ markewaite ] |
Assignee | Original: Mark Waite [ markewaite ] | New: Markus Winter [ mawinter69 ] |
Status | Original: In Progress [ 3 ] | New: In Review [ 10005 ] |
Remote Link | New: This issue links to "PR-325 switch authorize-project dependency back to a test dependency (Web Link)" [ 28854 ] |
Released As | New: 680.v3a_6a_1698b_864 | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: In Review [ 10005 ] | New: Resolved [ 5 ] |