Elevated CI artifact storage usage

In the context of tpo/tpa/team#41402 (closed) we've had to investigate storage usage linked to CI artifacts.

This project alone uses about 22 GB of storage in terms of CI artifacts, which represents 8% of the total available space.

Would it be possible to configure a tighter expiry for CI artifacts in this project via artifacts:expire_in, similar to what was implemented for Arti in its own .gitlab-ci.yml config?

Edited Nov 16, 2023 by Jérôme Charaoui

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information