[JIRA] (JENKINS-56834) Build permission on agents is not working

Build permission on agents is not working

Issue Type:	Bug
Assignee:	Oleg Nenashev
Components:	role-strategy-plugin
Created:	2019-04-01 14:42
Priority:	Critical
Reporter:	Luis Piedra-Márquez

Jenkins Version: 2.164.1

Role Strategy Plugin Version: 2.10

I configured a role with all agent related permissions: Build, Configure, Connect, Disconnect...

With this role assigned to a user, that user can Configure the agent, but it can't run builds on it. The cause of blockage indicates it lacks permissions to run on this slave.

It is related with the authorization strategy implementing the getACL for Computer but not for Node. If implementing the ACL also for Node apparently works without issues.

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

lpiedra@gmail.com (JIRA)

unread,

Apr 1, 2019, 2:55:02 PM4/1/19

to jenkinsc...@googlegroups.com

Luis Piedra-Márquez commented on

Pull Request: https://github.com/jenkinsci/role-strategy-plugin/pull/59

root@junwuhui.cn (JIRA)

unread,

Apr 3, 2019, 5:15:03 AM4/3/19

to jenkinsc...@googlegroups.com

runze xia commented on

Hi What is the log after the failure？ Luis Piedra-Márquez

lpiedra@gmail.com (JIRA)

unread,

Apr 3, 2019, 7:43:01 AM4/3/19

to jenkinsc...@googlegroups.com

Luis Piedra-Márquez commented on

No error logged.

It's just the build does not enter any slave altought it should have permissions to do so, and points it in the cause of blockage.

zentavr@trafford.com.ua (JIRA)

unread,

Jun 18, 2019, 1:07:03 PM6/18/19

to jenkinsc...@googlegroups.com

Andrey Miroshnichenko commented on

I have the same issue as well

svcjnks@keitalbame.net (JIRA)

unread,

Jul 24, 2019, 11:51:02 AM7/24/19

to jenkinsc...@googlegroups.com

Nuno Costa commented on

I also saw this happening. If I change the Project Default Build Authorization from RUN AS USER WHO TRIGGERED BUILD to RUN AS SYSTEM, it runs without any issue.

svcjnks@keitalbame.net (JIRA)

unread,

Jul 29, 2019, 10:19:02 AM7/29/19

to jenkinsc...@googlegroups.com

Nuno Costa edited a comment on

I also saw this happening. If I change the [Project Default Build Authorization|https://wiki.jenkins-ci.org/display/JENKINS/Authorize+Project+plugin] from RUN AS USER WHO TRIGGERED BUILD to *RUN AS* *SYSTEM*, it runs without any issue.

UPDATE: After doing some tweaking on Global and project roles permissions, I got it working with RUN AS USER WHO TRIGGERED BUILD, running the builds on Jenkins master.

wcleong@gmail.com (JIRA)

unread,

Sep 25, 2019, 12:07:04 AM9/25/19

to jenkinsc...@googlegroups.com

Wei Leong commented on

I'm experiencing the same issue as well. Nuno Costa would you mind sharing how you got it working with RUN AS USER WHO TRIGGERED BUILD?

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

arindom.sarkar@gmail.com (JIRA)

unread,

Sep 27, 2019, 12:38:02 PM9/27/19

to jenkinsc...@googlegroups.com

Arindom Sarkar commented on

Does anyone figured it out? How to resolve the issue?

svcjnks@keitalbame.net (JIRA)

unread,

Oct 1, 2019, 4:18:03 PM10/1/19

to jenkinsc...@googlegroups.com

Nuno Costa commented on

Wei Leong Arindom Sarkar From what I remembered, I had to provide general read and build privileges to the roles and then assign the users to those roles.