Is your job named Test-Slave? This works for me but I use Windows slaves
From: [email protected]
[mailto:[email protected]] On Behalf Of Andrew Barber
Sent: Friday, October 04, 2013 10:48 AM
To: [email protected]
Subject: Slave ${WORKSPACE} not set correctly
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]<mailto:[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.
