Details
-
Type:
New Feature
-
Status: Reopened (View Workflow)
-
Priority:
Minor
-
Resolution: Unresolved
-
Component/s: core
-
Labels:
-
Similar Issues:
Description
In our environment it would be very helpful to be able to set Permissions, who can see specific executors/slaves.
It should be like with jobs/projects, where the method "hasPermission()" is called, before you get all Items of the jenkins-instance.
So it would be just needed in the Computer.java a new attribute "Permission VIEW", and in the Jenkins.java in the Method "getComputer()" the check, if the user has the Permission to see this slave.
Attachments
Issue Links
- depends on
-
JENKINS-17200 SCM.TAG permission not eagerly loaded
-
- In Review
-
- is blocking
-
JENKINS-5517 Hudson to hide slave ids for Anonymous ID
-
- Open
-
- is related to
-
JENKINS-22760 Request for new slave-specific permission in Jenkins core
-
- Open
-
- relates to
-
JENKINS-15484 New permission controlling ability to configure your own User
-
- Open
-
- links to
This would be a good feature to have.
Using Folders, permissions and a few other plugins, our Jenkins is pretty much set in a "need to know basis", except for agents, which remain visible to any authenticated user.