Hi David You'd need to start them with different values of JENKINS_HOME at the very least. Personally I'd put them in separate tomcats running under separate users (JENKINS_HOME will default to ~/.jenkins). It'll use a bit more memory but the instances will be more independent (restarts, svn credentials etc).
If all you want is narrowing the jobs per team you ought to be able to achieve this using one instance and project-based security (though this would need a group to be added in the configuration of each job). Or if it's just UI convenience for users rather than a security concern you could prefix jobs names and use views with filters on. Good luck Brian On 16 March 2012 11:08, david <[email protected]> wrote: > Hello, I tried to start two instances of jenkins in a system by > TomCat, this is what i do: > 1: copy jenkins.war to tomcat/webapps, rename it to jenkins_1. > 2: copy and rename jenkins_1 to jenkins_2. > 3: start tomcat, then i can visit the two by: > http://localhost:8080/jenkins_1 > and http://localhost:8080/jenkins_2. > But i found some jobs which created by jenkins_1 was missing in job > list. The idea of multi-instances of jenkins, is because i want to > build a central CI server for each team, and they do not "see" the > others. > > Thanks~
