Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-50559

Authorization Folder property for Multibranch jobs

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      I would like to set up Authorization (Authorize Project plugin) for a Multibranch item. Setting up authorization at multibranch level is required to prevent branch projects to be able to build ANY project in the system.

        Attachments

          Activity

          allan_burdajewicz Allan BURDAJEWICZ created issue -
          jglick Jesse Glick made changes -
          Field Original Value New Value
          Component/s workflow-multibranch-plugin [ 21465 ]
          Description h3. Request

          I would like to set up Authorization ([Authorize Project plugin|https://plugins.jenkins.io/authorize-project]) for a Multibranch item. Setting up authorization at multibranch level is required to prevent branch projects to be able to build ANY project in the system.

          h3. Workaround

          A workaround is to set the Authorize project property from the Jenkinsfile but there is no special support for multibranch projects.
          I would like to set up Authorization ([Authorize Project plugin|https://plugins.jenkins.io/authorize-project]) for a Multibranch item. Setting up authorization at multibranch level is required to prevent branch projects to be able to build ANY project in the system.
          Labels authorization permissions authorization folders permissions pipeline
          Hide
          amirbarkal Amir Barkal added a comment -


          Any progress on this one?

          I have a very basic use case requiring this feature:
          Store and sync job definitions from scm (GitHub for example) using jobDSL syntax. Currently this seems to be impossible.

          For the jobDSL() step to work without forcing an administrator to approve changes manually, you need to run the jobDSL in sandbox mode. Sandbox mode works only when you configure a job to run as a specific user.

          Unfortunately the Authorize Project Plugin does not seem to support Multi-Branch pipeline job definition.

          Show
          amirbarkal Amir Barkal added a comment - Any progress on this one? I have a very basic use case requiring this feature: Store and sync job definitions from scm (GitHub for example) using jobDSL syntax. Currently this seems to be impossible. For the jobDSL() step to work without forcing an administrator to approve changes manually, you need to run the jobDSL in sandbox mode. Sandbox mode works only when you configure a job to run as a specific user . Unfortunately the Authorize Project Plugin does not seem to support Multi-Branch pipeline job definition.
          Hide
          daxroc Damien Roche added a comment -

          Running into the same use case as Amir Barkal has mentioned above.

          Show
          daxroc Damien Roche added a comment - Running into the same use case as Amir Barkal has mentioned above.
          Hide
          michelzanini Michel Zanini added a comment -

          I have two folders that will be visible and accessible by different users.
          To avoid a pipeline step to trigger a job on the other folder I can't run jobs with the default SYSTEM user.
          I need to use Authorize Project plugin to change to run with a specific user.
          However, how can I configure a folder and sub-items to run with a specific user?
          I can only do that on Global Jenkins level, but I need to override the global definition on this 2 folders.
          The ticket here mentions support for multi-branch pipelines, I guess normal folders also apply. Possibly implementing for one will do for the other.

          Show
          michelzanini Michel Zanini added a comment - I have two folders that will be visible and accessible by different users. To avoid a pipeline step to trigger a job on the other folder I can't run jobs with the default SYSTEM user. I need to use Authorize Project plugin to change to run with a specific user. However, how can I configure a folder and sub-items to run with a specific user? I can only do that on Global Jenkins level, but I need to override the global definition on this 2 folders. The ticket here mentions support for multi-branch pipelines, I guess normal folders also apply. Possibly implementing for one will do for the other.

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            allan_burdajewicz Allan BURDAJEWICZ
            Votes:
            16 Vote for this issue
            Watchers:
            19 Start watching this issue

              Dates

              Created:
              Updated: