-
Improvement
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins ver. 1.596.2, Ubuntu 12.04
The current option "Use Github repository permissions" says:
If checked will use github repository permissions to determine jenkins permissions for each project.
Public projects - all authenticated users can READ. Only collaborators can BUILD, EDIT, CONFIGURE or DELETE.
Private projects, only collaborators can READ, BUILD, EDIT, CONFIGURE or DELETE
For private repos there are 3 access levels: pull (read) access, push (write) access and admin access.
It would be much better to give people will pull access READ permission, people with push access READ/BUILD permission and READ, BUILD, EDIT, CONFIGURE or DELETE only to admins.
- is duplicated by
-
JENKINS-45188 Github oAuth Plugin not give rights to user for Github Organization Project
- Closed
-
JENKINS-33661 Plugin permissions not supported
- Closed
-
JENKINS-42509 authenticated team members should have read/build permissions when using Github Committer Authorization Strategy
- Closed
-
JENKINS-63421 Agent/Connect and other Agent permissions
- In Progress
-
JENKINS-43078 Admin users could be defined as organization*team too
- Closed
-
JENKINS-45168 Grant EXTENDED READ rights to collaborators/admins on a Github repo
- Closed
-
JENKINS-41632 workspaces are still visible to anyone with READ access
- Closed
-
JENKINS-52956 GitHub Commiter Authorization Strategy - allow users with WRITE to stop builds
- Closed
- relates to
-
JENKINS-33661 Plugin permissions not supported
- Closed
-
JENKINS-40566 Allow non-admins ability to cancel or abort builds when using "GitHub Committer Authorization Strategy"
- Closed