Terje Andersen edited a comment on New Feature JENKINS-18741

@Oleg
Where I work we have a Jenkins Master, and I was just asked to add a group to the ownership of a job, meaning that the members of a group can change the Job Configuration and run the Job.

We are using Single Sign-On in front of the Master, where the user identity and groups are fetched via environment variables ( reverse-proxy-auth-plugin ).
We are also using Role Strategy Plugin ( role-strategy ).

I managed it now, by:
1. Setting the @ItemSpecific and @ItemSpecificWithUserId roles in "Manage Jenkins" > "Manage And Assign Roles" > "Manage Roles"
2. Assigning both roles (@ItemSpecific, @ItemSpecificWithUserId) to the group in question in "Manage Jenkins" > "Manage And Assign Roles" > "Manage Roles"
3. Going to "<my-job>" > "Manage Ownership" > "Configure specific access rights" and giving full access to the group in question (ticking all checkboxes).

  • What I struggle to understand is why I need to do step 1 and 2, and not only 3 to give the members of a group access to edit the job configuration and run it.
  • The access rights I set in step 3 would indicate that the users of the group could delete the Job, but I guess that's limited to the Project Roles I defined in step 1, correct?

Maybe this isn't the correct place to ask for this, we can move it to the Jenkins Users google group? And yes, I am new with Jenkins

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to