When using SSH jobs users might experience limitations that are specific for Windows operating systems. One reason for such limitations is the fact that SSH is not available with the OS but is implemented by third party products.

• A complete re-write of the JITL SSH Job is provided by
  

  Jira
  server SOS JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 6dc67751-9d67-34cd-985b-194a8cdc9602 key JITL-123

   

• Display feature availability
  StartingFromRelease 1.9

Windows Based Systems:

CopSSH:

When using this JITL job please consider our experiences with some SSH products for Windows.

Copssh

Copssh CopSSH is a Windows SSH Service based on the Linux SSH Implementation OpenSSH provided by Itefix in collaboration with Cygwin. Newer Versions of CopSSH do not support the cmd.sh any more. The "Windows Shell" We experienced the following limitations when using Copssh 5.0.3:

• Interactive Shell
  • Problem
    • The Windows shell can only be used as an interactive shell and does not support command or script executions.
    • The reason for this behavior is the fact that newer versions of CopSSH do not support the non-interactive shell cmd.sh any more.
    • For details see https://www.itefix.net/content/windows-shell-sftp.
  • Solution

  ...

  • • • Using the "Bash and sFTP shell" with Copssh will work

  ...

  • • • for Windows

  ...

  • The Windows command
    • • systems when using the cygwin supported Linux commands.
    • Examples

  ...

  • • for Limitations
      • Limitation: the Windows command 
    • • set will not be recognized
    - use
    • • . 
        • Workaround: use export instead.
    The
    • • Limitation: the %
    special
    • •  special character to mark an environment variable such
    as
    • • as %VARIABLENAME%
    will
    • •  will not be recognized.
        • Workaround:
    use $VARIABLENAME instead.Executing
    • • • use $VARIABLENAME instead.
        • Hint: be careful when using mixed case spelling for environment variables.
      • Limitation: executing chained Windows commands in one line with the command
    delimiter
    • • delimiter &
    or
    • •  or &&
    will
    • •  will result in executing only the first command.
    Use
    • • • Workaround: use the Linux command delimiter ";"
    together
    • • •  together with the proper Linux command instead.
    Prefixing
    • • Limitation: prefixing a command
    with
    • • with cmd /C
      won´t work either.
    • •  does not execute the specified command.
        • Workaround: 
          • prüfen: http://stackoverflow.com/questions/17582778/how-to-execute-a-bat-file-from-cygwin-bash-that-uses-the-windows-find-command
          • evtl. auf Artikel verlinken;  geht denn 

            cmd /C start "clean shell" /I "${EXPLORER_WINPATH}" "${SCRIPT_WINPATH}"

            Beispiel: start "My Notepad" /I c:/tmp/hallo.cmd

  bitvise SSH Server

  ...

  • Environment Variables
    • Limitation: setting environment variables

  ...

  • • with set would not allow using this variable

  ...

  • • in further commands

  ...

  • • .
    • Example:

  ...

  • • unsuccessful use of an environment variable

  ...

  • • in a subsequent command:
      • set TESTFILE=test.txt

  ...

  • • • echo MYPARAM=myTestParam >> %TESTFILE%

  Instead, it results in:

  ...

  • • • This example shows that %TESTFILE% is not substituted, instead a file with the name %TESTFILE% is being created and MYPARAM=myTestParam is being written to that

  ...

  • • • file.

    named test.txt with this entry.