If I try to use xshell with a parameter field that is coded with forward slashes, it is okay if the command line is typed that way directly in the xshell Commandline fidle in the Jenkins configuration - these forward slashes get converted to backslashes for Windows. But if I store the same string with forward slashes in a variable, and use the variable on the xshell commandline, then the contents of the variable do not get the forward slashes converted to backslashes for Windows. It seems that the variable is not substituted for its value before doing the platform conversion of slashes.
PARAMETER_WITH_FORWARD_SLASHES : //windows/lan/location
xshell commandline: echo A Windows path not using variable is //windows/lan/location, but using a variable is $PARAMETER_WITH_FORWARD_SLASHES.
Results from Jenkins run:
Started by user rickybobpat
[EnvInject] - Loading node environment variables.
Building remotely on jen_slave (winx64 windows) in workspace c:\cygwin\local\builds\pm\j3\workspace\Test xshell
[Test xshell] $ cmd.exe /C "echo A Windows path not using variable is "\\windows\lan\location," but using a variable is %PARAMETER_WITH_FORWARD_SLASHES%. && exit %%ERRORLEVEL%%"
A Windows path not using variable is "\\windows\lan\location," but using a variable is //windows/lan/location.