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

Build permission on agents is not working

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      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.

       

       

       

        Attachments

          Activity

          Hide
          ncosta Nuno Costa added a comment -

          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.

          Show
          ncosta Nuno Costa added a comment - 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.
          Hide
          gradol Oliver Grad added a comment - - edited

          Are there any news on that issue?

          I can reproduce it. All permissions set in the node-role are working (configure, connect, disconnect) except the build permission.

          We need this feature to restrict the usage of some special build nodes (setting global build permission on Agent is therefore not an option).

          Are there any other solutions for that scenario?

          The setup is Jenkins 2.249 and Role-based Authorization Strategy-Plugin 3.0

          Show
          gradol Oliver Grad added a comment - - edited Are there any news on that issue? I can reproduce it. All permissions set in the node-role are working (configure, connect, disconnect) except the build permission. We need this feature to restrict the usage of some special build nodes (setting global build permission on Agent is therefore not an option). Are there any other solutions for that scenario? The setup is Jenkins 2.249 and Role-based Authorization Strategy-Plugin 3.0
          Hide
          vinhdqhp QV added a comment -

          We really need this feature. Kindly review and resolve this bug please.

          Show
          vinhdqhp QV added a comment - We really need this feature. Kindly review and resolve this bug please.
          Hide
          samica Frederico Pratas added a comment - - edited

          I'm facing the same issue, slave A owned by user X is not accepting jobs from the user.

          The output is:

          'X' lacks permission to run on 'A'

           

          Jenkins 2.253
          Role-based Authorization Strategy v3.0

          Show
          samica Frederico Pratas added a comment - - edited I'm facing the same issue, slave A owned by user X is not accepting jobs from the user. The output is: 'X' lacks permission to run on 'A'   Jenkins 2.253 Role-based Authorization Strategy v3.0
          Hide
          tkleiber Torsten Kleiber added a comment -

          On my staging jenkins system this works fine, but not on my production system. I don't see the responsible difference in both configurations.

          Show
          tkleiber Torsten Kleiber added a comment - On my staging jenkins system this works fine, but not on my production system. I don't see the responsible difference in both configurations.

            People

            Assignee:
            oleg_nenashev Oleg Nenashev
            Reporter:
            luispiedra Luis Piedra-Márquez
            Votes:
            11 Vote for this issue
            Watchers:
            18 Start watching this issue

              Dates

              Created:
              Updated: