When using the new feature in V5.6 to clone a deployment environment, one of the SSH tasks which has internal scripts fails. It appears somehow not to recognize environment variables that have been set within the SSH script.

After opening the SSH task, then copying and pasting the original script from the source deployment environment and replacing the "cloned" SSH script, the task runs without a problem.

In the attached logs, the log from the original task is successful, with files being copied to the deployment area. (long list deleted for brevity)

In the cloned task log, there are problems that show "error" in the log in the column to the left, and messages like "bad substitution". Files do not get copied, and deployment fails (even though exit code shows "success"..don't know why it doesn't fail as it clearly has "error" in the log, but that is a separate issue).

The steps that I took to reproduce the problem on my system is:

1) After upgrade to 5.6, run a working deployment environment to make sure upgrade works.
2) Go into Edit Environment for the working deployment environment, and "Clone" to a new environment.
3) Run the cloned environment, and examine log and observe that files were not copied as expected, and found "error" on several log statements.