The reason is that regular projects archive artifacts as last step, and you probably don't want to show / allow downloading a partial archive. So any solution will need to ensure that the current archiving action has been completed.
The reason is (my guess) that regular projects archive artifacts as last step, and you probably don't want to show / allow downloading a partial archive. So any solution will need to ensure that the current archiving action has been completed.
Jesse Glick Someone downloads artifacts. Let's ignore the possibility that it'll result in half-archived files / broken archives when a file is still being written to, there's still a chance that the archive is incomplete if some files are not yet finished. Now there's an archive around that doesn't have all the things in it. Seems like there's only pain and suffering in that direction.
I thought we could view archived artifacts before. In our workflow, I've been holding a parallel step open to keep a VM around until the developer could look at the failure and triage it (cloud causes the VM to go poof as soon as the node is done). We upload logs before an input stage; now they aren't visible.
Matthias Balke, where do you see the download icon? I have a prompt dialog in my pipeline and when it's waiting for a user's response, nobody can see archived artifacts.
Do you know any workarounds? Is it possible to write own function in a shared library that will attach files to the build immediately?
It’s here, not on the page where you see details about a specific build but on the page above that one, where you see information about all builds in a branch or project.