Thanks

Ah, good find. The file browser is the only component of the web app that would use the SSH client directly, and it looks like those dlls just aren't getting packaged correctly in the installer. We'll put this on the list to fix.

Here are the actions that aren't supported via SSH agent currently: Unit Test Actions HTTP Reporting Actions Generate Release Notes Action (unless running on BuildMaster server) Execute Database Change Scripts Action Rename Files Action (shell script is recommended for this) Set File Attributes Action (shell script is recommended for this)

Thanks for the pointers, Dean!

You are correct - I had a typo in the working directory !. This question can be closed.

The "Execute Command Line" option correctly handles the return code from the unix command so we can use this option, thanks. It would be good if the SSH Execute options worked, however, as they give us some more flexibility. Note, the target Unix platform where the return code is not handled is Solaris 10.