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

Agent Role Pattern Not Finding Matching Agent

XMLWordPrintable

      This bug report details an issue encountered with the Jenkins Role-Based Access Plugin. When attempting to define an Agent role in the Manage Roles section, the provided role pattern fails to identify matching agents.

      Steps to Reproduce:

      1. Access Jenkins and navigate to "Manage Jenkins."
      2. Click on "Manage and Assign Roles."
      3. Go to the "Manage Roles" section.
      4. Create a new role or edit an existing one.
      5. Under the "Agent" permissions, enter "master" as the role pattern.
      6. Double-click on the "master" pattern.

      Expected Behavior:

      Double-clicking on the "master" pattern should display a list of agents matching the pattern (presumably an agent named "master").

      Actual Behavior:

      Double-clicking on the "master" pattern results in a message indicating "no agent found matching 'master'."

        1. image-2024-07-18-18-24-03-008.png
          image-2024-07-18-18-24-03-008.png
          178 kB
        2. image-2024-07-18-18-20-18-575.png
          image-2024-07-18-18-20-18-575.png
          254 kB
        3. image-2024-07-08-10-38-39-773.png
          image-2024-07-08-10-38-39-773.png
          58 kB
        4. image-2024-07-08-10-38-20-575.png
          image-2024-07-08-10-38-20-575.png
          139 kB
        5. image-2024-07-08-10-35-48-188.png
          image-2024-07-08-10-35-48-188.png
          19 kB
        6. image-2024-07-08-10-35-26-152.png
          image-2024-07-08-10-35-26-152.png
          59 kB
        7. image-2024-07-08-10-34-03-902.png
          image-2024-07-08-10-34-03-902.png
          67 kB
        8. image-2024-07-05-16-43-24-453.png
          image-2024-07-05-16-43-24-453.png
          30 kB
        9. image-2024-07-05-16-42-31-339.png
          image-2024-07-05-16-42-31-339.png
          53 kB
        10. image-2024-07-05-19-09-43-992.png
          image-2024-07-05-19-09-43-992.png
          134 kB
        11. image-2024-07-05-19-06-51-030.png
          image-2024-07-05-19-06-51-030.png
          170 kB

          [JENKINS-73407] Agent Role Pattern Not Finding Matching Agent

          Sudarshan T N created issue -

          Markus Winter added a comment -

          Please provide more input, e.g. a screenshot listing the agents that are defined (from .../computer) would be helpful

          Is your intention to define permissions on the built-in agent?

          Markus Winter added a comment - Please provide more input, e.g. a screenshot listing the agents that are defined (from .../computer) would be helpful Is your intention to define permissions on the built-in agent?
          Markus Winter made changes -
          Assignee Original: Oleg Nenashev [ oleg_nenashev ] New: Markus Winter [ mawinter69 ]
          Sudarshan T N made changes -
          Attachment New: image-2024-07-05-19-06-51-030.png [ 62939 ]
          Sudarshan T N made changes -
          Attachment New: image-2024-07-05-19-09-43-992.png [ 62940 ]

          Sudarshan T N added a comment -

          Sudarshan T N added a comment -

          Sudarshan T N added a comment - - edited

          define permission for master and cloud agents

          Sudarshan T N added a comment - - edited define permission for master and cloud agents

          Markus Winter added a comment - - edited

          remember that you have to use regular expressions, so 

          (?i)restricted-agent*

          should probably be 

          (?i).*restricted-agent.*

          This will not match labels given to agents.

          And 'master' will only match an agent with name 'master'. As mentioned before the controller itself is not using the term 'master' anymore.

           

           

          Markus Winter added a comment - - edited remember that you have to use regular expressions, so (?i)restricted-agent* should probably be (?i).*restricted-agent.* This will not match labels given to agents. And 'master' will only match an agent with name 'master'. As mentioned before the controller itself is not using the term 'master' anymore.    
          Markus Winter made changes -
          Attachment New: image-2024-07-05-16-43-24-453.png [ 62942 ]
          Attachment New: image-2024-07-05-16-42-31-339.png [ 62943 ]

          Sudarshan T N added a comment -

          thank you it worked 

          Sudarshan T N added a comment - thank you it worked 

            mawinter69 Markus Winter
            sudarshan Sudarshan T N
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: