[JIRA] (JENKINS-16077) ${WORKSPACE} environment var is relative on slaves if jenkins root path isn't explicitly set

[cr...@2ndquadrant.com (JIRA)]

Craig Ringer created JENKINS-16077 ${WORKSPACE} environment var is relative on slaves if jenkins root path isn't explicitly set Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 08/Dec/12 10:03 AM Description: If a job's UNIX shell script references the environment variable ${WORKSPACE}, it's always an absolute path when the job runs on the master, but it's a relative path when the job runs on a slave - and it's the wrong relative path, because it's relative to the jenkins root, not to the CWD the job script is run in. I've traced this to the fact that my slaves don't have an explicit jenkins root path set. They do their work in the $HOME of the user Jenkins ssh's in as. Jenkins should be prepending its cwd to the working path if no explicit root path was configured. On one of my workers for example, ${WORKSPACE} resolves to: workspace/pg_master_multiplatform/label_arch/x64/label_os/amazonlinux201209 where it should be : /home/ec2-user/workspace/pg_master_multiplatform/label_arch/x64/label_os/amazonlinux201209 Environment: Jenkins is on Java SE 6 on Debian 6 x64. The issue appears on any UNIX slave, but not on the master. Project: Jenkins Priority: Minor Reporter: Craig Ringer

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