Strategy for using slave nodes in Jenkins for a full LDAP/NFS Linux-setup

[Peter Toft]

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

[Peter Toft]

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? :-)