bamboo scp task with artifact not working as expected: creates remote dir from the destination path of the artifact


we have an artifact from another plan containing a directory structure, like


We want to scp the files of this artifact.

To do this we first define an "Artifact download configuration" task in our plan to make the artifact known to the scp task. Without that we are not able to choose this artifact in the artifact-selectbox of the scp task, right?
In the "Artifact download configuration" task we define a destination path "foobar" for our artifact.

If we define a remote path like "/home/user/conf" the scp task creates


but we expect to get


If we define an empty destination path we get more files than we wanted since our base directory contains other files beside the files from our artifact.

Any help?

Shouldn't the scp task support the definition of a working directory or otherwise ignore the destination path from the "Artifact download configuration" task?

Answer from another topic suggesting to use the script task:

Best regards


1 answer

If the artifact does not contain any subdirectories it works as expected. Perhaps the same problem as in

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Jan 15, 2019 in Statuspage

Introducing Statuspage Getting Started guides! First up: What is Statuspage?

Over the next several weeks we'll be sharing some of our Getting Started guides here in the community. Throughout this series of posts, we'd love to hear from customers and non-customers ab...

297 views 5 2
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you