-
Notifications
You must be signed in to change notification settings - Fork 295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Buildkite CLI can not download Buildkite artifact #2150
Comments
Official docs mention that recreating all files matching the uploaded file paths can be accomplished with:
Unfortunately, moving to the destination directory and downloading to
|
Hi @gw0. Sorry that you are experiencing this. We are intending to overhaul how artifacts upload and download works. But in the meantime, can you contact [email protected] and provide a build where this is happening so that we can debug it more thoroughly. |
It turned out this are the consequences of some ill-designed logic in the Buildkite CLI. Docs describe it as: "If the last path component of matches the first path component of your , the last component of is dropped from the final path." |
Gee, that's quite unexpected behaviour, but someone somewhere may be relying on it. It's quirks like this that have motivated our intention to replace the artifact upload/download subcommands with something that does not carry this baggage. However, that's going to take some time to develop. If you're still blocked, let us know, and we can see what we can do in the interim. |
The solution was to first check if checksum of already cached artifacts match, otherwise download to a temporary directory and then move to final destination. |
Is your feature request related to a problem? Please describe.
The Buildkite CLI is failing to download artifacts. Official docs describe the command:
Describe the solution you'd like
According to the docs to download the artifact
myapp
intogo/myapp/myapp
I would expect the following command to work (the destination is the directory with a trailing slashgo/myapp/
):It is attempting to download the artifact to
go/myapp
instead ofgo/myapp/myapp
. Of course the destination is a directory, this is why I explicitly indicated this with the trailing slash.Describe alternatives you've considered
I would expect that by not specifying the trailing slash, I can indicate the destination file
go/myapp/myapp
explicitly:Of course the destination file does not exist yet, because I have not downloaded it yet.
Additional context
/
The text was updated successfully, but these errors were encountered: