Issue Summary 

When the Artifact download task downloads the artifacts to a folder that is expanded from a Bamboo variable, the SCP task fails to copy the file to the remote SSH server in case the “Artifact -> Artifact Name” option is used.

This is reproducible on Data Center: (yes)

Steps to Reproduce

1. Created a deployment project and an environment later added task.
2.  In artifact download task, under destination path defined a variable ${bamboo.deploy.project}
3. Added another task of scp, to copy the artifact to another location, which got failed chose the “Artifact -> Artifact Name” option.
4. Whereas the path is present on the bamboo server from where it is trying to copy the files.
5. When we add a script task to display the variable it is substituting the variable correctly whereas only in scp task its not resolving them.

Expected Results

Able to upload the files to the target location and deployment should get successful.

Actual Results

The below exception is thrown in the build.log file as well on deployment logs shown in UI:

The task will be executed on the following hosts: 192.168.100.134
29-Feb-2024 08:12:15Connecting to 192.168.100.134 on port: 22
29-Feb-2024 08:12:15Error occurred while running Task 'test(3)' of type com.atlassian.bamboo.plugins.bamboo-scp-plugin:scptask.
29-Feb-2024 08:12:15/opt/atlassian/bamboo-home/local-working-dir/1179650-1277954/${bamboo.deploy.project} does not exist.  

Workaround

Replace the variable with direct path or use "Artifact -> local files" as a workaround