Limitations when using SSH jobs for Windows

FEATURE AVAILABILITY STARTING FROM RELEASE 1.9

Windows Based Systems:

CopSSH:

CopSSH is a Windows SSH Service based on the Linux SSH Implementation OpenSSH in collaboration with Cygwin.

Newer Versions of CopSSH do not support the cmd.sh any more. The "Windows Shell" can only be used as an interactive shell and does not support command or script executions - see https://www.itefix.net/content/windows-shell-sftp .

However, the "Bash and sFTP shell" will work on Windows Systems when using the cygwin supported Linux commands.

Examples:

• The Windows command set will not be recognized - use export instead.
• The % special character to mark an environment variable such as %VARIABLENAME% will not be recognized: use $VARIABLENAME instead.
• Executing chained Windows commands in one line with the command delimiter & or && will result in executing only the first command. Use the Linux command delimiter ";" together with the proper Linux command instead.
• Prefixing a command with cmd /C  won´t work either.

bitvise SSH Server:

Setting environment variables with set works, but using this variable for further commands won´t work.

Example:

Setting a file name as an environment variable (works):

set TESTFILE=test.txt

Calling a command using this variable (doesn´t work):

echo MYPARAM=myTestParam >> %TESTFILE%

Instead, it results in:

A File with the name %TESTFILE% being created and MYPARAM=myTestParam being written to that file, which is the opposite to the desired behavior of creating a file named test.txt with this entry.