[martypitt]

I might be alone, but I'm really struggling with this line of fixes from Gitlab.

To be clear - I'm all for Gitlab charging, I think that's fair and reasonable.

However, if they're gonna charge for artifact storage, they need to provide first-class tooling to manage the storage.

My experience is almost exactly the same as the OP's. Huge artefact storage from builds, the scripts to clean up don't work.

> The async operation to delete artifacts can take a while. How do I tell if something has succeeded or failed then? Last time I ran the scripts, no errors were mentioned, but nothing was tidied up.

Cleaning this stuff up shouldn't be via hacky scripts or community projects. It should be a mandatory requirement for managing an aspect of my account that's about to become very very expensive.

[nakedgremlin]

Oh it feels great to learn I'm not alone in this problem. I completely agree with everything noted here.

The current interface provided for removing the artifacts on GitLab just does not work. There is no feedback; no confirmation. We just uncheck a box and just cross our fingers since there is no other step noted.

Even with the new guidance provided, it's still additional jumps through other codebases just to see if it works. I'm now worried that if I go through this new process, I'll end up right back at the same issue.