[JIRA] (JENKINS-50559) Authorization Folder property for Multibranch jobs

[aburdajewicz@cloudbees.com (JIRA)]

Allan BURDAJEWICZ created an issue

Jenkins / JENKINS-50559 Authorization Folder property for Multibranch jobs Issue Type: New Feature Assignee: Unassigned Components: authorize-project-plugin, workflow-multibranch-plugin Created: 2018-04-04 03:36 Labels: permissions authorization Priority: Major Reporter: Allan BURDAJEWICZ Request 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. Workaround A workaround is to set the Authorize project property from the Jenkinsfile but there is no special support for multibranch projects. Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[jglick@cloudbees.com (JIRA)]

Jesse Glick updated an issue

Jenkins / JENKINS-50559 Authorization Folder property for Multibranch jobs

Change By: Jesse Glick Component/s: workflow-multibranch-plugin Labels: authorization folders permissions pipeline 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.

Add Comment

[amirbarkal@sparkbeyond.com (JIRA)]

Amir Barkal commented on JENKINS-50559

Re: Authorization Folder property for Multibranch jobs 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.

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[dcroche@gmail.com (JIRA)]

Damien Roche commented on JENKINS-50559

Re: Authorization Folder property for Multibranch jobs

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

Add Comment

[michelzanini@gmail.com (JIRA)]

Michel Zanini commented on JENKINS-50559

Re: Authorization Folder property for Multibranch jobs

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.

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)