Usually it is desireable if everyone who commits to a software repository also has access to the Jenkins that builds from the repository. At least with the lean/agile methodologies which are popular these days, every committer is responsible for his commits. If someone's commit breaks the build, he is expected to fix it ASAP. If only select people have access to Jenkins, the committer who broke the build might learn about it only when someone with access to Jenkins tells him.
But there are of course many ways to develop software. -- Sami Tim Pizey kirjoitti 4.7.2012 kello 15.01: > Hi Sami, > > Thankyou for you clear explanation. > > I would really like to see Committers and Users separated out. > They are not necessarily both People. > > The Committer scavenging messes up my Users. > > cheers > Tim > > > On 4 July 2012 09:50, Sami Tikka wrote: >> It depends. By default (= security is off) the people list is just the >> committers Jenkins has seen in the builds it has made. >> >> If you turn on security, you can also add people into the list. >> >> If you set a password for a person, that person can log in. >> >> What is the nature of the DOUBT you are having? >> >> -- Sami >> >> Varghese Renny kirjoitti 4.7.2012 kello 8.24: >> >>> >>> >>> Hi, >>> i am having doubt regarding the people display in jenkin's people >>> link. On what basis the people are showing in the people.. >>> Today i noticed that even username of my system(slave) is showing inside >>> people link. Also username i used for commit.(credentials). Please tell me >>> regarding the userid and name on the people link of jenkins. >>> >>> >>> Thanks in advance >>> varghese >> > > > > -- > Tim Pizey - http://pizey.net/~timp
