Hi John This is a simple problem, if we dont try to over-kill it. Each SCM has its own user files to authenticate transactions, please dont confuse between system/scm accounts. Both are separate.
Hence, create service, for example, i created, jenkins-pan for our company, i just make sure, this user account has enough access to check-out/commit for any branch that jenkins builds(even other teams should give enough access for this scm account if they want CI Builds) Hope i made sense. thanks, Krishna Chaitanya On Tue, Jul 24, 2012 at 2:21 PM, JohnL <john.lengel...@gmail.com> wrote: > I am new to Jenkins... > > I am trying to figure out how to setup jenkins on top of our existing > builds which are run out of cron. We have a specific user account which > is used for all builds and tests. (user: otto, group: dev). This specific > user belongs to the group which is needed to access the source code > repository. > > Should I setup Jenkins to run as user "jenkins" and group "jenkins" and > then have jobs setup to run the builds using our build account? What > about when Jenkins is polling the source control system. Would it need to > be a member of group "dev"? Would it be better to setup the Jenkins user > account to be by default using the group "dev"? > > It also appears that other development groups may be using other > user/group accounts to run builds and access source repositories. So what > ever I setup, I need to be able to handle these builds using their build > accounts. > > Any guidance for me? > > TIA, > > johnl >
