Hello,

We are implementing Master/Slave model of Jenkins for our organization.

It will be having 1 master and 4 slaves, everything running on Centos 
servers.

Right now we have 12 different project running 12 different Jenkins 
installations on 12 different servers, and now we are merging everything to 
one.

 

My plan is like create a different view on master for every project and 
push them to slaves. So at the end I will have 12 views.

 

But my problem is , I don't want project A people to see Project B jobs. In 
short I need view level access , so that I can give access to person to 
particular view only. There can be cases where a person is working on 1 or 
more projects for this, he must see 2 views when he login with his ID.

 

 

Eg:

my organization have 12 projects, Tom works on Project A , Raj works on A 
and B project.

So when Tom login we only see project A view. Rest 11 view must not be 
visible to him.

When Raj logins we must be able to see A and B ,rest 10 must be invisible 
to him.

 

Note: we use LDAP for this.

 

 

Looking forward for your guidance on same. It would be great if you can 
share step for the same.

 

Reply via email to