[JIRA] (JENKINS-12667) No possibility to specify "Workspace Root Directory" for Slave node

Mon, 01 Oct 2012 02:41:22 -0700

 
ciaranj edited a comment on Bug JENKINS-12667

I looked into this myself as I would like to have a set of VMs each running a jenkins slave (single executor) but all building to and from the same disk. (I'm running into problems with disk space due to multiple copies of the same job sitting redundantly on each VM's disk, as the same job (for me) never builds con-currently I can't see a reason why I shouldn't be able to do this [disk IO performance aside])

But because the location of the Jenkins Slave (JENKINS_HOME) is intrinsically linked to the location of the workspace (JENKINS_HOME/workspace) (on slaves anyway) I can't have all those slaves sharing the same workspace folder at the moment, as they would all try (and fail) to overwrite their working files in the JENKINS_HOME location (e.g. jenkins-slave.out, jenkins-slave, slave.jar). (FTR I've tried sym-linking each slave's 'workspace' folder to the shared disk but to compound things msysgit then appears to stop cloning!)

It looks like there was an intention to implement this in JENKINS-8446 but a deliberate decision was made to avoid this Is it worth me spending anytime implementing this, or would that effort just be rejected as it isn't part of the intended strategy?
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to