Bind Usergroup to specified node(s)/slave(s)?

20 views
Skip to first unread message

Dan Steffen

unread,
Apr 25, 2016, 1:44:42 PM4/25/16
to Jenkins Users
Hello,

we start at office to work with one central-master jenkins server for the administration (job-definitions, user management etc.) and one or more nodes per team, this works without problems. But we look for a configuration so we could bind the nodes to the usergroups we use to organized the teams so not a team can use the nodes of another team.

I already found out that you can defined the node at the job, but in the best case the Teams can defined the jobs by there own. I don't know if I explained it very well what is our goal. But if somebody understand our problem I would very thankful for every useful hint.
best regards

Daniel Beck

unread,
Apr 25, 2016, 3:01:33 PM4/25/16
to jenkins...@googlegroups.com

> On 25.04.2016, at 19:44, 'Dan Steffen' via Jenkins Users <jenkins...@googlegroups.com> wrote:
>
> we start at office to work with one central-master jenkins server for the administration (job-definitions, user management etc.) and one or more nodes per team, this works without problems. But we look for a configuration so we could bind the nodes to the usergroups we use to organized the teams so not a team can use the nodes of another team.
>
> I already found out that you can defined the node at the job, but in the best case the Teams can defined the jobs by there own. I don't know if I explained it very well what is our goal. But if somebody understand our problem I would very thankful for every useful hint.

Authorize Project Plugin lets you define the Jenkins user account a job is considered to be running as – by default, it's considered SYSTEM/unrestricted. Coupled with the Agent/Build permission configurable e.g. in (project-based) Matrix Auth strategies, you can restrict the nodes a build can be executed on.
https://wiki.jenkins-ci.org/display/JENKINS/Authorize+Project+plugin

Job Restrictions Plugin allows you to define which jobs are allowed to run on each node based on e.g. job name.
https://wiki.jenkins-ci.org/display/JENKINS/Job+Restrictions+Plugin

My employer's CloudBees Jenkins Enterprise includes the Folders Plus Plugin, that allows restricting which builds can run on a node based on the folder they're in.
https://documentation.cloudbees.com/docs/cje-user-guide/foldersplus-sect-controlledslaves.html

Dan Steffen

unread,
Apr 29, 2016, 11:50:46 AM4/29/16
to Jenkins Users, m...@beckweb.net
Hello,

excuse my late response the Job Restrictions Plugin was exactly that was i looking for. Thanks for your help
best regards
Dan
Reply all
Reply to author
Forward
0 new messages