You can continue using Role Strategy. Just define a new role with global permission Overall/Read only (so they can access Jenkins and log in), and then add access selectively per project. Your existing users then probably need to get a new role that grants them Job/Read globally.
On 20.02.2015, at 16:28, Eric Wood <
eric...@rocketmail.com> wrote:
> I assume that "enable project-based security" is the same as "project based matrix authorization strategy". Under here I can set access for uses based on "view". Is this the section for specifying what jobs a user can and cannot see?
>
>
>
>
> On Friday, February 20, 2015 9:50 AM, Luís Borges de Oliveira <
l...@siscog.pt> wrote:
>
>
> On 20-02-2015 13:25, Eric Wood wrote:
> > I've been asked to create a Jenkins instance that would be opened up
> > to several of our clients so they can log in and run jobs that impact
> > only their environment. I am unaware of how to securely segment jobs
> > so only certain jobs are visible to certain clients. Internally I use
> > Role-Base Strategy to be able to authorize certain tasks to certain
> > users, but they have read capability to everything.
>
> In your job settings, you can "Enable project-based security" and there
> you'll be able to define what certain users and groups can read.
> (Namely, there's the "Anonymous" user.)
>
> HTH,
> Luís
>
> --
> 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
> To unsubscribe from this group and stop receiving emails from it, send an email to