-
Notifications
You must be signed in to change notification settings - Fork 720
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
Uploading a single file #3
Comments
you can't since we use the artifact name as a folder to hold all uploaded files. |
@TingluoHuang I think that counts as a feature request :) |
@os6sense agreed, the UI could have some pop-up dialog to allow you download individual file within your artifact. |
IMHO, this action could/should:
For example:
would create:
Ideally, the GUI would allow to download each file separately OR a tarball of each of the sections ('Packages' and/or 'Docs', in these examples), as suggested by @TingluoHuang. EDIT Related to #5, each of the files or sections should also have a 'remove' button, only visible to maintainers. Ideally, it would be possible to reorganize the content of the 'artifacts folder'. I.e., move items from a section to another. |
Yup, would love to be able to upload files instead. my build process already ends with a zip file and currently this action would just zip the zip. |
This is worse with any non-zip package/tarball. For zips I extract them, so they are compressed again. However, for tar.gz, you get double compression. |
@damccorm any plans for that? |
I would also love to be able to specify an already made zip or other single file instead of getting zip containing a zip |
Bump |
This issue and #7 sum up ~100 reactions. @chrispat, @TingluoHuang, @madhurig, might we have an update about the status of this enhancement request? |
Also, I had a process which produced a |
Ideally you could upload files uncompressed and be able to reference them by url. That way you could include screenshots within markdown of a status check / comment. |
This would be fantastic. In particular, the current zipping does not preserve symlinks or the executable bit. |
hello all |
At the minimum, if the artifact is just a single file, the web interface shouldn't ZIP the file. Pass the raw file with the proper MIME type so if I upload a PDF or JPEG, I can just click it on the Actions tab and view it in my browser without unzipping it. Unfortunately this seems to be a common theme with GitHub. Issues that I would consider show-stoppers or at least significant quality of life improvement are just rotting or getting closed without any time table except for "its on the back burner". If I could download individual items via the web or get the URLs from the API, we would likely need to pay GH for more storage. Instead I'll likely just use an S3 bucket and pay Amazon to store my stuff. They will let me set retention policies and a storage class so I can control my costs. |
@konradpabjan are there any updates on this? would be nice to have this feature in 2022. thanks |
Yes, this will create a zip inside a zip due to how actions/upload-artifact@v3 currently works. See actions/upload-artifact/issues/3 in GitHub for details. But it will let me inspect the result of the release zip without having to create a release.
Any progress on this? Being able to download a non-zipped artifact is absolutely vital. |
I would also like this feature of downloading the uploaded artifact if its a single file as it is. It is annoying when it zips an already zipped file. I would really appreciate if it is implemented! |
> Upload-artifact not working for steps running in containers #13 Is this supported added? |
I would like to have this feature. |
I would really really like to have this feature! |
I really want this feature |
If this is a UI problem, then the solution would be for the UI to detect and modify its download action as follows:
Who maintains the UI? Is it part of this repository? |
Do we have any solution for this problem? |
Upload it somewhere -anywhere- else. Even nightly.link gives you zip files, so artifacts are not the solution here. |
+1 for this feature request... :P |
Needed! |
We pay for storage to use it. Stop being petty. |
Just to be clear, I'm not affiliated with github, that was just me telling you what we're stuck with. As of now, our best option to enable direct downloads is to upload it somewhere else. For example, make a separate repo, and have your CI push artifacts onto that repo's release page. Or push it onto netlify, or an R2 bucket (which has no egress fees). Sidenote while i'm already posting: every "+1" or "needed" is sending notifications to at least 40 people. please just use the reactions on the original comment. |
Caveats: - curl tool resides under `subdir/bin/` inside the package. Can be fixed locally by renaming curl to unique names, e.g. `curl-x64.exe` or `curl-riscv64`. Maybe even to a more globally unique name, such as `curl-linux-musl-amd64`. - curl tool misses the exec permission so cannot be executed after unzipping. Needs `chmod +x` before doing so. https://github.com/actions/upload-artifact#permission-loss actions/upload-artifact#38 - There is no option to switch to tarball from zip. - there is no option to skip zip and offer files as-is. (exec attribute would be lost in this case as well) actions/upload-artifact#39 actions/upload-artifact#3 (closed) actions/upload-artifact#14 (pending upload-artifact@v4) 3-4 years old unresolved issues on the side of GitHub.
Caveats: - curl tool resides under `subdir/bin/` inside the package. Can be fixed locally by renaming curl to unique names, e.g. `curl-x64.exe` or `curl-riscv64`. Maybe even to a more globally unique name, such as `curl-linux-musl-amd64`. - curl tool misses the exec permission so cannot be executed after unzipping. Needs `chmod +x` before doing so. https://github.com/actions/upload-artifact#permission-loss actions/upload-artifact#38 - There is no option to switch to tarball from zip. - Uploading a `.tar.gz` will still get it zipped by GitHub. - there is no option to skip zip and offer files as-is. (exec attribute would be lost in this case as well) actions/upload-artifact#39 actions/upload-artifact#3 (closed) actions/upload-artifact#14 (pending upload-artifact@v4) 3-4 years old unresolved issues on the side of GitHub.
Caveats: - curl tool resides under `subdir/bin/` inside the package. Can be fixed locally by renaming curl to unique names, e.g. `curl-x64.exe` or `curl-riscv64`. Maybe even to a more globally unique name, such as `curl-linux-musl-amd64`. - curl tool misses the exec permission so cannot be executed after unzipping. Needs `chmod +x` before doing so. https://github.com/actions/upload-artifact#permission-loss actions/upload-artifact#38 - There is no option to switch to tarball from zip. - Uploading a `.tar.gz` will still get it zipped by GitHub. - there is no option to skip zip and offer files as-is. (exec attribute would be lost in this case as well) actions/upload-artifact#39 actions/upload-artifact#3 (closed) actions/upload-artifact#14 (pending upload-artifact@v4) 3-4 years old unresolved issues on the side of GitHub.
They contain curl tool executables only, without static libs, shared lib and other bits. Caveats: - curl tool resides under `subdir/` inside the package. Can be fixed locally in the future by renaming curl to unique names, e.g. `curl-x64.exe` or `curl-riscv64`. Maybe even to a more globally unique name, such as `curl-linux-musl-amd64`. - curl tool misses the exec permission so cannot be executed after unzipping on *nix systems. Needs `chmod +x` before doing so. https://github.com/actions/upload-artifact#permission-loss actions/upload-artifact#38 - there is no option to switch to tarball from zip. - uploading a `.tar.gz` will still get it zipped by GitHub. - there is no option to skip zip and offer files as-is. (exec attribute would be lost in this case as well) actions/upload-artifact#39 actions/upload-artifact#3 (closed) actions/upload-artifact#14 (pending upload-artifact@v4) - a workaround for most of this is uploading them to our own server in the exact form we want. 3-4 years old unresolved issues on the side of GitHub.
Caveats: - curl tool resides under `subdir/bin/` inside the package. Can be fixed locally by renaming curl to unique names, e.g. `curl-x64.exe` or `curl-riscv64`. Maybe even to a more globally unique name, such as `curl-linux-musl-amd64`. - curl tool misses the exec permission so cannot be executed after unzipping. Needs `chmod +x` before doing so. https://github.com/actions/upload-artifact#permission-loss actions/upload-artifact#38 - There is no option to switch to tarball from zip. - Uploading a `.tar.gz` will still get it zipped by GitHub. - there is no option to skip zip and offer files as-is. (exec attribute would be lost in this case as well) actions/upload-artifact#39 actions/upload-artifact#3 (closed) actions/upload-artifact#14 (pending upload-artifact@v4) 3-4 years old unresolved issues on the side of GitHub.
Say I wish to upload a screenshot made from puppeteer, can it be possible to upload just the image generated rather than a zip file only containing that image.
The text was updated successfully, but these errors were encountered: