Thank you so much! It also seems additive - so if I add everyone to the job with read-only perms, it's in addition to their global permissions?
On Thursday, August 29, 2013 7:16:20 PM UTC-4, Daniel Beck wrote: > > This is desired behavior in Project-based Matrix security. Try adding a > user/group with no permissions on a specific job. This no-op entry will > simply disappear when saving. Permissions granted globally cannot be > revoked on specific jobs using this security strategy. > > You could use Role Strategy Plugin, and specify the 'global level' using a > regular expression with negative lookahead, thereby matching all projects > except a few. > > Alternatively, commercial Jenkins Enterprise has Role-based Access > Control, which allows you to filter (global) roles so they don't apply to a > specific project. > > On 29.08.2013, at 22:01, Maven User <maven....@gmail.com <javascript:>> > wrote: > > > Hi all - > > > > I want to allow all users at the global level to do a few things BUT for > a particular job, I only want a few people to be able to run it. > > > > I seems like once at a global level, if "authenticated users" have been > granted access to run a job then on a per job basis, I can't specify a > subset. > > > > Is this the desired behaviour or am I missing the boat a bit? > > > > -- > > 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 jenkinsci-use...@googlegroups.com <javascript:>. > > For more options, visit https://groups.google.com/groups/opt_out. > > -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
