title: Inconsistent Jenkins workspace path on slave machines
body: <p>We have some jobs set up which share a workspace.  The workflow for the various branches is:</p>
  
  <ul>
  <li>Build a big honking C++ project called <code>foo</code>.</li>
  <li>Execute several downstream tests, each of which uses the workspace of <code>foo</code>.</li>
  </ul>
  
  <p>We accomplish this by assigning the <code>Use custom workspace</code> field of the downstream jobs to the build workspace.</p>
  
  <p>Recently, we took one branch and assigned it to be build on a Jenkins slave machine rather than on the master.  I was surprised to find that on master, the <code>foo</code> repository was cloned to <code>$JENKINS_JOBS_PATH/FOO/workspace/foo_repo</code> - while on the slave, the repository was cloned to <code>$JENKINS_JOBS_PATH/FOO/foo_repo</code>.</p>
  
  <p>Is this by design, or have we somehow configured master and slave inconsistently?</p>