Slave permissions and limiting which jobs a given slave will execute

[Jeff Thornsen]

Hello all,

I tried to search for answers to this, but didn't come up with anything obvious.

We have a shared Jenkins instance which is used by multiple teams.

Using the CloudBees Folder plugin (the Free version), I created folders in Jenkins for both TeamA and TeamB, and set up appropriate permissions
* Only members of GroupA can see TeamA Folder and the jobs within
* Only members of GroupB can see TeamB Folder and the jobs within

I also have 2 slaves, SlaveA and SlaveB


Is there an easy way for me to configure SlaveA to only run jobs configured under the TeamA folder?
Ideally, SlaveA would also only be visible in the web GUI to members of GroupA.

I could not find any obvious mechanism for setting slave-level permissions to accomplish this.
I could come up with a custom solution involving slave labels, but this would require members of TeamA to specify that label in each of their jobs, which I would like to avoid.


I have not yet explored the Ownership Plugin or any of the other Role-Based Authorization plugins.

I also haven't looked into the Enterprise (paid) plugins from CloudBees to see if they offer something that could do this for us.


Thanks for any advice you can give!
-Jeff

[Daniel Beck]

On 21.11.2014, at 23:57, Jeff Thornsen <jtho...@gmail.com> wrote:

> I also haven't looked into the Enterprise (paid) plugins from CloudBees to see if they offer something that could do this for us.

Cloudbees Folders Plus does exactly that.