I tend to run all my builds on slaves. - make sure the workspace on slaves is different from that on the master - have a recent version of java on the slave - be able to ssh to it and our .cshrc should throw any error's or messages to the terminal when you get there Slaves need to be able to get to your git/SVN servers.
You don't need tomcat to run a jenkins master. You can run it natively. >java --jar jenkins.war & Backup $JENKINS_HOME on the master. It is all you need. Have Fun Frank On Tuesday, December 11, 2012 3:33:09 PM UTC-8, Jeff Vincent wrote: > > I'm starting to setup a new master/slave configuration using Ubuntu 12.10 > + Tomcat 7. I couldn't find any real docs regarding slaves and could use > some clarification on best practices particularly with tools. > > My builds use: > > Git or SVN > Maven > SVN > Java 6 and 7 > > Additionally I have configured ANT for some legacy projects (that I may > not convert) and with maven I use SONAR and the maven release plugin. > > What is the best practice for getting a slave configured? > > So far, the issues I've had relate to configuring GIT, git ssh-key auth, > and Maven settings. I'm sure the list will continue. > > Any help is appreciated to make this less painful... > > -- > Jeff Vincent > preda...@gmail.com <javascript:> > See my LinkedIn profile at: > http://www.linkedin.com/in/rjeffreyvincent > I ♥ DropBox <http://db.tt/9O6LfBX> !! > >
