Job artifacts taking too much disc space

Hello,
I have been seeing how quickly the size of job artifacts grows and takes up alot of space on the instance.
I placed an expiration policy, but it only applies to new artifacts and since anyone can overwrite it at project level, it does not solve the issue still. Reading this GitLab article gives an option of manually removing job artifacts.
However, I want to ask how do you resolve this issue? Do you simply follow the options in the GitLab article, or do you have some script that does the cleaning for you periodically?

Thank you for taking the time to read my question. :slight_smile:

This is one of the tasks for which the included tools are seriously inadequate, and an area where I think it shows that GitLab is focused on providing features developers might want over features administrators need.

We did some scary database queries to make old artifacts look expired, luckily it’s been years since we did that and we haven’t had issues with developers setting a high value for artifact expiration.

1 Like