Closed bradrydzewski closed 7 years ago
I will take it.
@bradrydzewski Try the following config:
+ strip_components: 1
target: /usr/local/bin/
source: release/some-binary
Remove the specified number of leading path elements.
It would be great if this were mentioned in the docs, I just spent an hour or two searching for this before going through the issues by hand.
@b12f See https://github.com/drone/drone-plugin-index/pull/81 and the latest document here
@appleboy looks great! Also, thanks for writing the plugin.
I have config:
target:
- /root/project
source:
- run.sh
- config/dev/conf
I want:
/root/project/run.sh
/root/project/conf
When I use strip_components=2, the "run.sh" file is missed
So I suggest to use a bool param to decide whether tar parent directory when tar files
When I have config:
target:
- /home/deploy/web1
- /home/deploy/web2
source:
- release_1.tar.gz
- release_2.tar.gz
Should I supposed copy release_1.tar.gz to web1 and release_2.tar.gz to web2 ? But result is both release_1.tar.gz and release_2.tar.gz are in web1 and web2
I have the following configuration
It copies
release/some-binary
to/usr/local/bin/release/some-binary
If I were using scp, I would expect that it copies
release/some-binary
to/usr/local/bin/some-binary
and does include the source path in the target destination.