This is related to JENKINS-3997, which reported that custom-workspace doesn't expand parameters.

      What I did:
      I set the custom workspace to %BRANCHNAME%\Test_Job, where %BRANCHNAME% is a parameter.

      Expected Result:
      When BRANCHNAME is set to 'default', I expect the custom workspace to be expanded to 'default\Test_Job'

      Current Result:
      The output log looks like this:

      Console Output (with Mercurial)

      Started by user anonymous
      $ hg clone --rev default --noupdate http://myrepo/Scripts D:\Tools\Jenkins%BRANCHNAME%\Test_Job
      abort: The system cannot find the path specified: D:\Tools\Jenkins\default\Test_Job\.hg
      ERROR: Failed to clone http://myrepo/Scripts
      WARN: Revision data for previous build unavailable; unable to determine change log
      Finished: FAILURE

      Console Output (with SVN)

      Started by user anonymous
      Checking out a fresh workspace because D:\Tools\Jenkins%BRANCHNAME%\Test_Job_SVN doesn't exist
      Cleaning local Directory Test_Job_SVN
      Checking out http://myrepo/svn/sdk
      A lib
      A lib\vc8
      A lib\vc8\x64_Release
      AU lib\vc8\x64_Release\mytestlib_x64_release.pdb
      AU lib\vc8\x64_Release\myTestLib_x64_Release.lib
      AU lib\vc8\x64_Release\mylib_x64_release.pdb
      AU lib\vc8\x64_Release\mylib_x64_Release.lib
      A lib\vc8\Win32_Release
      ...
      ...
      At revision 1773
      no revision recorded for http://myrepo/svn/sdk in the previous build
      Finished: SUCCESS

      I ran it for both SVN and Mercurial just to verify that this behaviour is consistent with different SCM's.

          [JENKINS-12206] Parameter in Custom Workspace

          Vite Falcon added a comment -

          I just wanted to add that the version of Jenkins I'm using right now is 1.444 and I've seen this behaviour since 1.38*

          Vite Falcon added a comment - I just wanted to add that the version of Jenkins I'm using right now is 1.444 and I've seen this behaviour since 1.38*

          Vite Falcon added a comment -

          BUMP... Is no one else experiencing this issue?

          Vite Falcon added a comment - BUMP ... Is no one else experiencing this issue?

          vjuranek added a comment -

          Hi, I tried with latest 1.451 and works fine, could you please confirm? Thanks

          vjuranek added a comment - Hi, I tried with latest 1.451 and works fine, could you please confirm? Thanks

          evernat added a comment -

          No response from the reporter, so resolving as incomplete.
          Please reopen if the issue is still reproduced.

          evernat added a comment - No response from the reporter, so resolving as incomplete. Please reopen if the issue is still reproduced.

            Unassigned Unassigned
            vitefalcon Vite Falcon
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: