We're updating the issue view to help you get more done. 

Fined grained ACL permissions for jobs and builds

Description

will introduce a new permission to limit users that can trigger builds from Jira, but it would be nice if user driven actions in Jira that have impact on Jenkins are controlled via an ACL or other means where an administrator in Jira can limit permissions to either Jira users, groups or project roles.

Environment

None

Activity

Show:
WuHao
January 16, 2020, 6:48 AM

Hello,

Currently, when Jira user trigger a build, he could see and trigger all Jenkins jobs, this is very dangerous.

I suggest that, Jira system admin and Jira admin could configure which jenkins job is visible for current Jira project user, so that he can only trigger the jenkins job which only belongs to his project.

 

As a workaround, I hide the button "trigger a build", and our team trigger build by commit source code to Bitbucket.

I am very very expect that "Jenkins Integration for Jira" could develop this feature, so that I can make a perfect workflow for our devops.

 

Hugo Wu

 

Assignee

Unassigned

Reporter

Mark Rekveld

Labels

None

Epic/Theme (migrated)

None

Business Value (migrated)

None

Patch submitted

None

Testcase(s) included

None

Components

Affects versions

Priority

Major
Configure