Hi,
we have an artifact from another plan containing a directory structure, like
file1.txt
dir1/file2.txt
dir2/file3.txt
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
/home/user/conf/foobar/file1.txt
/home/user/conf/foobar/dir1/file2.txt
/home/user/conf/foobar/dir2/file3.txt
but we expect to get
/home/user/conf/file1.txt
/home/user/conf/dir1/file2.txt
/home/user/conf/dir2/file3.txt
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: https://answers.atlassian.com/questions/19145752
Best regards
Achim
If the artifact does not contain any subdirectories it works as expected. Perhaps the same problem as in https://answers.atlassian.com/questions/11981587
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.