Role-based Authorization Strategy has unnecessary dependence on Authorize Project plugin

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • 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.

            Assignee:
            Markus Winter
            Reporter:
            James Holderness
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: