Thanks guys, I'll take a look at the ownership/Job restrictions plugins. That might be something that could work.
I'll have to shy away from the Authorize plugin for now as it doesn't play nice with some other plugins and breaks some major credential pugins functionality (or at least it did, maybe its been fixed) Cheers Matt On Tuesday, August 15, 2017 at 12:07:35 PM UTC-4, Oleg Nenashev wrote: > > There are few more simple ways if you just need this feature: > > - Use Authorize Project plugin > <https://wiki.jenkins.io/display/JENKINS/Authorize+Project+plugin> to > assign authentication to your builds. Then Just set Computer/Build > permissions for you nodes (Can be done in Role Strategy plugin for example) > - Use Job Restrictions Plugin > <https://wiki.jenkins.io/display/JENKINS/Job+Restrictions+Plugin> to > restrict access to node via Node properties > > You can find some pointers to plugins and sample configurations in this > slidedeck: > https://speakerdeck.com/onenashev/belarus-jenkins-meetup-managing-security-in-jenkins-with-config-as-code-and-roles > > > BR, Oleg > > > > вторник, 15 августа 2017 г., 15:35:22 UTC+2 пользователь Victor Martinez > написал: >> >> https://wiki.jenkins.io/display/JENKINS/Ownership+Plugin might help you >> to define who owns those nodes/jobs and so on. >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/a1de6de8-8dff-4e75-8ac2-c3ed96e020ed%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
