Details
-
Bug
-
Resolution: Fixed
-
Medium
-
9.1.0, 9.2.4
-
None
-
2
-
Severity 2 - Major
-
2
-
Description
Issue Summary
Remote path in SCP Task is not getting updated with the Destination directory from the artifact defination
This is reproducible on Data Center: (yes) / (no) yes
Steps to Reproduce
- Create a Script taks which generates an artifact say "Training"
- Create a artifact defination.
- Mark this as shared
- Create a second stage under this stage create a new job
- In the new job define the artifact dependency as "Training" as created above
- Define the destination directory as ${bamboo.buildResultKey}
- Add a scp task to this second stage with appropiate host, authentication methods
- Select the artifact Training in the scp task
- Select the remote path as /tmp/
Expected Results
The artifacts are transferred over to the remote server under path /tmp/${bamboo.buildResultKey}
Actual Results
The ${bamboo.buildResultKey} value is not getting placed in the remote location and the artifacts are getting stored in the /tmp/ folder of the remote machine .
Workaround
1. Create an ssh task just before the scp task to ssh to the remote machine and " mkdir ${bamboo.buildResultKey}"
2. Configure the Remote path as "/tmp/${bamboo.buildResultKey}"
Attachments
Issue Links
- mentioned in
-
Page Loading...