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

Build permission on agents is not working

XMLWordPrintable

    • 508.v2a_f05b_05e9d8

      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.

       

       

       

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

          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

          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

          QV added a comment -

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

          QV added a comment - We really need this feature. Kindly review and resolve this bug please.

          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

          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

          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.

          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.

          Oliver Grad added a comment -

          A Happy New Year.

          Are there any news on this issue.

          It's still reproducable, now on Jenkins 2.274 and Role-based Authorization Strategy-Plugin 3.1.

          Oliver Grad added a comment - A Happy New Year. Are there any news on this issue. It's still reproducable, now on Jenkins 2.274 and Role-based Authorization Strategy-Plugin 3.1.

          Oliver Grad added a comment -

          Found a solution for our specific case.

          Using Job Restrictions Plugin will meet our needs.

          Oliver Grad added a comment - Found a solution for our specific case. Using Job Restrictions Plugin will meet our needs.

          Brian added a comment -

          I am experiencing this same issue. Setting "Project Default Build Authorization" to "Run as User who triggered build" causes jobs to hang with the message "user lacks permissions to run on node"

          Brian added a comment - I am experiencing this same issue. Setting "Project Default Build Authorization" to "Run as User who triggered build" causes jobs to hang with the message "user lacks permissions to run on node"

          ethorsa added a comment -

          Me too since a few days ago.

          • Jenkins v2.303.1
          • Role Strategy Plugin v3.2.0

          ethorsa added a comment - Me too since a few days ago. Jenkins v2.303.1 Role Strategy Plugin v3.2.0

          Gautier BEGIN added a comment -

          Are there any news on this issue ?

          Gautier BEGIN added a comment - Are there any news on this issue ?

          Markus Winter added a comment -

          PR #194 will fix the issue

          Markus Winter added a comment - PR #194 will fix the issue

            oleg_nenashev Oleg Nenashev
            luispiedra Luis Piedra-Márquez
            Votes:
            16 Vote for this issue
            Watchers:
            26 Start watching this issue

              Created:
              Updated:
              Resolved: