How to "unkeep" artifacts?
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Hi! Unsure if this is just a documentation issue, or maybe the feature is missing, but we have a hard time understanding how to undo the "Keep" button on Job artifacts.
So I set this with the "Documentation" template, but it may be wrong.
Problem to solve
There is a keep button on Jobs artifacts which allows to bypass the expiration date:
Yet there is seemingly no way to "unkeep" the artifacts, not even if you have direct link to the job (no "unkeep", "release" or "delete" button). This is a first issue.
A second issue is that even if there was a way from the job page, we need a "Kept job summary" page, to have a larger view of older artifacts we might have kept and delete them later. We are not going to keep artifacts forever!
Further details
Use case: we use Gitlab on GNOME instance for the project GIMP. We have a lot of space issue because of the many commits a week which create new artifacts through the CI each and every time. So we have to set a very low expiration date, which would be very fine if we can also sometimes keep some odd CI build results (for instance to ask someone to test a specific build but we are not sure when one can test).
The "Keep" button looks like it is exactly for this purpose, cf. the docs.
Yet there seems to be no way to find back the various kept artifacts later on to undo them. And since we have space issues, we don't want to keep random artifacts without possibility of deleting them later obviously. What am I missing?
Proposal
It would be nice to have:
- A "Release" button which replace the "Keep" button once we clicked on it. "Release" obviously does the opposite of "Keep" which means let it expire of normal expiration rule).
- Some page somewhere on Gitlab to list all the "kept" artifacts so that we can manually delete them (when we haven't kept a link to kept jobs).
Maybe this does exist and then it's a documentation issue. Or it doesn't but there is another way to manage these artifacts (still a documentation issue). Or finally there is no way currently, then it's a feature request (if not a bug report, because wasting half a GiB here, half a GiB there each time someone hits the "Keep" button as we would end up with never-deleted artifacts, and no way to reclaim the space, seems like a huge waste).