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,
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
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 clie
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 Strate
