[ 
https://issues.jenkins-ci.org/browse/JENKINS-12206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159471#comment-159471
 ] 

vjuranek commented on JENKINS-12206:
------------------------------------

Hi, I tried with latest 1.451 and works fine, could you please confirm? Thanks
                
> Parameter in Custom Workspace
> -----------------------------
>
>                 Key: JENKINS-12206
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-12206
>             Project: Jenkins
>          Issue Type: Bug
>          Components: core
>    Affects Versions: current
>         Environment: Platform: x64, OS: Windows
>            Reporter: Vite Falcon
>            Priority: Blocker
>              Labels: custom-workspace, jenkins, windows
>
> This is related to 
> [JENKINS-3997|https://issues.jenkins-ci.org/browse/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:
> {panel:title=Console Output (with Mercurial)|
> titleBGColor=#00FFCC|
> bgColor=#CCFFCC}
> 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
> {panel}
> {panel:title=Console Output (with SVN)|
> titleBGColor=#00FFCC|
> bgColor=#CCFFCC}
> 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
> {panel}
> I ran it for both SVN and Mercurial just to verify that this behaviour is 
> consistent with different SCM's.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to