I can at least see that having a special "Remote root directory" per slave unit costs that my projects are cloned from my git server from scratch. Good thing? Bad thing? :-)
On Tuesday, January 27, 2015 at 11:30:25 AM UTC+1, Peter Toft wrote: > > Hi all > > I have been updating my lovely Linux-based Jenkins setup with a set of new > compute nodes. > It seems to work just fine to add a new node Jenkins -> nodes -> New node > (at http://jenkins:8080/computer/) and my jobs are transferred using SSH. > All works now :-) > > I have a "jenkins" server and 3 slave hosts "slave1", "slave2" and > "slave3", > > My setup has NFS for all hosts (same jenkins directory - we replaced > /var/jenkins with /home/jenkins/) > and we have the same user accounts setup via LDAP. > But I have one thing that I do not understand properly (please comment): > > For any of the slave machines (e.g. slave1) in > http://fpc-jenkins:8080/computer/slave1/configure I have a field > "Remote root directory" which I currently set to /home/jenkins/slave/slave1 > for the slave1 machine and > /home/jenkins/slave/slave2 for the slave2 machine. > > Should I - or can I - set this directly to /home/jenkins/ for all of the > slave machines? > Any pitfalls here? > > Thanx mates > > /pto > > > > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/94405bc3-7b5b-4b35-8cf4-dadeed3dd744%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
