[JIRA] (JENKINS-12667) No possibility to specify "Workspace Root Directory" for Slave node
Title: Message Title twolfart commented on JENKINS-12667 Re: No possibility to specify "Workspace Root Directory" for Slave node Thanks for the hint, pmv. For our usecase we decided to set the workspace for the affected jobs to avoid a global change of the workspace folder. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12667) No possibility to specify "Workspace Root Directory" for Slave node
Title: Message Title
pmv commented on JENKINS-12667
Re: No possibility to specify "Workspace Root Directory" for Slave node
We set the master jenkins 'Workspace Root Directory' to
${ITEM_ROOTDIR}/w
And then in the slave config, we set the 'Remote root directory' to
D:\j
So then the workspaces are in 'D:\j\w' - probably about as short as you can get. If you have multiple slaves on one machine, you set the 'Remote root directory' to a different letter, and end up with 'D:\h\w', etc. Doing it on the master node means your linux slaves also use 'w' instead of 'workspace', even though they don't need the shortened version, but that's not a big deal in my opinion.
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12667) No possibility to specify "Workspace Root Directory" for Slave node
Title: Message Title twolfart commented on JENKINS-12667 Re: No possibility to specify "Workspace Root Directory" for Slave node As ridiculous as it may sound, but with Windows and some of its build tools still not being able to use more then 248 chars, saving a few digits with switching from "workspace" to "w" would be great. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12667) No possibility to specify "Workspace Root Directory" for Slave node
Title: Message Title Bradley Cooley commented on JENKINS-12667 Re: No possibility to specify "Workspace Root Directory" for Slave node Are there any current plans for implementing this soon? Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-12667) No possibility to specify Workspace Root Directory for Slave node
ciaranj edited a comment on JENKINS-12667 No possibility to specify Workspace Root Directory for Slave node 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
[JIRA] (JENKINS-12667) No possibility to specify Workspace Root Directory for Slave node
ciaranj commented on JENKINS-12667 No possibility to specify Workspace Root Directory for Slave node 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) 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
[JIRA] (JENKINS-12667) No possibility to specify Workspace Root Directory for Slave node
ciaranj edited a comment on JENKINS-12667 No possibility to specify Workspace Root Directory for Slave node As an update, further reading of the code has shown that it is possible to achieve what I (and possible the issue author requests through specifying a system property on startup of the jenkins master node. I've updated my jenkins startup script to pass: -Dhudson.model.Slave.workspaceRoot=e:/ This is interpreted seperately from the JENKINS_HOME variable so I'm able to have separate local jenkins working files, but a shared disk location for all the slave workspaces(in my case the E: drive, note the value passed can be absolutely specified or specified relatively to JENKINS_HOME), which is exactly what I wanted to achieve. Be aware this will affect all nodes however! 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
[JIRA] (JENKINS-12667) No possibility to specify Workspace Root Directory for Slave node
[ https://issues.jenkins-ci.org/browse/JENKINS-12667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=160184#comment-160184 ] Oleksandr Popov commented on JENKINS-12667: --- I mean not Jenkins root folder (cause Remote FS root parameter is jenkins itself root) but workspace directory for each job. For master server it is possible to specify single directory for all jobs where SCM do checkout for all branches. You could find this variable if you go: Manage Jenkins - Configure System - Press Advanced buttom in the top of configuration screen - you will see Workspace Root Directory property. Thanks for your assistance in advance! No possibility to specify Workspace Root Directory for Slave node --- Key: JENKINS-12667 URL: https://issues.jenkins-ci.org/browse/JENKINS-12667 Project: Jenkins Issue Type: Bug Components: slave-setup Affects Versions: current Environment: Jenkins 1.452 Reporter: Oleksandr Popov Assignee: Oleksandr Popov Priority: Critical There is no possibility to specify Workspace Root Directory for Slave node as it is for Master node. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12667) No possibility to specify Workspace Root Directory for Slave node
[ https://issues.jenkins-ci.org/browse/JENKINS-12667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159997#comment-159997 ] Frederik Fromm commented on JENKINS-12667: -- Hmmm... in the node configuration page computer/node name/configure there is a field Remote FS root where you define the workspace root directory on a slave. Is this what you are looking for? The slave setup plugin uses the Remote FS root directory to copy the files to and from where the script can be executed. No possibility to specify Workspace Root Directory for Slave node --- Key: JENKINS-12667 URL: https://issues.jenkins-ci.org/browse/JENKINS-12667 Project: Jenkins Issue Type: Bug Components: slave-setup Affects Versions: current Environment: Jenkins 1.452 Reporter: Oleksandr Popov Assignee: Kohsuke Kawaguchi Priority: Critical There is no possibility to specify Workspace Root Directory for Slave node as it is for Master node. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12667) No possibility to specify Workspace Root Directory for Slave node
[ https://issues.jenkins-ci.org/browse/JENKINS-12667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleksandr Popov updated JENKINS-12667: -- Environment: Jenkins 1.452 (was: Jenkins 1.450) Priority: Critical (was: Major) No possibility to specify Workspace Root Directory for Slave node --- Key: JENKINS-12667 URL: https://issues.jenkins-ci.org/browse/JENKINS-12667 Project: Jenkins Issue Type: Bug Components: slave-setup Affects Versions: current Environment: Jenkins 1.452 Reporter: Oleksandr Popov Assignee: Kohsuke Kawaguchi Priority: Critical There is no possibility to specify Workspace Root Directory for Slave node as it is for Master node. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12667) No possibility to specify Workspace Root Directory for Slave node
[ https://issues.jenkins-ci.org/browse/JENKINS-12667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=159740#comment-159740 ] Oleksandr Popov commented on JENKINS-12667: --- Any update? No possibility to specify Workspace Root Directory for Slave node --- Key: JENKINS-12667 URL: https://issues.jenkins-ci.org/browse/JENKINS-12667 Project: Jenkins Issue Type: Bug Components: slave-setup Affects Versions: current Environment: Jenkins 1.450 Reporter: Oleksandr Popov Assignee: Kohsuke Kawaguchi There is no possibility to specify Workspace Root Directory for Slave node as it is for Master node. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-12667) No possibility to specify Workspace Root Directory for Slave node
Oleksandr Popov created JENKINS-12667: - Summary: No possibility to specify Workspace Root Directory for Slave node Key: JENKINS-12667 URL: https://issues.jenkins-ci.org/browse/JENKINS-12667 Project: Jenkins Issue Type: Bug Components: slave-setup Affects Versions: current Environment: Jenkins 1.450 Reporter: Oleksandr Popov Assignee: Kohsuke Kawaguchi There is no possibility to specify Workspace Root Directory for Slave node as it is for Master node. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
