Scope

• 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 concerning limitations with some SSH products for Windows. Before posting a support request please check the following behavior of your SSH server and verify by use of a command line tool if possible SSH issues were related to the SSH server or to the JITL job.
• The list of products and limitations is not complete, please contact your SSH server vendor for details.

Copssh

Copssh CopSSH is a Windows SSH Service based on the Linux SSH Implementation implementation OpenSSH provided by Itefix in collaboration with Cygwin. Newer Versions of CopSSH don´t 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

...

• • • execution.
    • The reason for this behavior is the fact that CopSSH does not support the non-interactive shell cmd.sh.
    • 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 special character %
    • • Limitation: the % special character to mark an environment variable
    like
    • • such as %VARIABLENAME%
    will
    • •  will not be recognized
    , use $VARIABLENAME instead.
    • • .
        • Workaround: use $VARIABLENAME instead.
        • Hint: be careful when using mixed case spelling for environment variables.
      • Limitation: executing
    Executing
    • • chained Windows commands in one line with the command
    delimiter
    • • delimiters &
    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.
      • Limitation: prefixing a command with cmd /C does not execute the specified command.
        • Workaround: 
          • check: http://stackoverflow.com/questions/17582778/how-to-execute-a-bat-file-from-cygwin-bash-that-uses-the-windows-find-command

  probably link to the article, is
  cmd /C start "clean shell" /I "${EXPLORER_WINPATH}" "${SCRIPT_WINPATH}"

  working?

   

  • • • • • example: start "My Notepad" /I c:/tmp/hallo.cmd
  • • • • • tested:
            • with cygstart -w launcher.bat ./test.cmd 
            • cygstart has to be available, it is not integrated in the Copssh installation, but available through the standard cygwin installation
              
              • nothing happens in the ssh connection
              • JUnit Test fails with exit code 127
            •  with cmd /C
    won´t work either.
  • • • • • • start /I ./test.cmd
              • • nothing happens in the ssh connection
              • JUnit Test hangs as soon as the command will be executed remotely

   

  bitvise SSH Server

  ...

  • Environment Variables
    • Limitation: setting environment variables

  ...

  • • with set would not allow using this variable

  ...

  • • in further commands

  ...

  • • .

  example:

  • • Example: unsuccessful use of an environment variable

  ...

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

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

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

  will result 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.

   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.