Have you tried 1.535 (or any later release)? It would be helpful to confirm that it hasn't already been fixed before a developer spends any time on this.
----- Original Message ----- From: [email protected] To: [email protected] At: Oct 4 2013 11:31:31 I should mention that I am running the master and the slave on linux. AJ On Friday, October 4, 2013 10:47:40 AM UTC-4, Andrew Barber wrote: Has anyone else seen this? (I am on 1.529) When a jobs is launched on a slave, ${WORKSPACE} is set to the slave root instead of the workspace directory. I setup a simple example with a project that does echo ${WORKSPACE} pwd The project is a basic project - the only selection changed from the default is "Restrict where this project can be run" which I set to my slave. Here is the console for the job. You can see the difference between ${WORKSPACE} and pwd. [EnvInject] - Loading node environment variables. Building remotely on XL-build1 in workspace /home/scratch/jenkins_xl/workspace/Test-Slave [Test-Slave] $ /bin/sh -xe /tmp/hudson4075547965590808000.sh + echo /home/scratch/jenkins_xl /home/scratch/jenkins_xl + pwd /home/scratch/jenkins_xl/workspace/Test-Slave The only work-around I have found is to set a custom workspace, but that doesn't work if I need to allow concurrent builds. I filed a bug on this issue a week ago, but haven't gotten any bites. AJ -- 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]. For more options, visit https://groups.google.com/groups/opt_out. -- 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]. For more options, visit https://groups.google.com/groups/opt_out.
