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 don´t support the cmd.sh any more. The „Windows Shell“ can only be used as an interactive shell and doesn´t 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 like %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%

will result in:

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