[Gitlab.com] Cleanup policy for tags is disabled for veloren/veloren

Dear Gitlab.com Admins,

I am Owner of the veloren/veloren repository at gitlab.com and when looking at the “Project Overview” page it tells that we are using up 66GB of data.
We are a open source project and very happy to use gitlab.com, but we were wondering if we may be spaming the storage of your hosting and cleaning up (SOME!) of those GB might help you save a few bucks.

It says 66GB, but there is no breakdown in “Repository” “LFS” “Docker Registry”.
As we are building a docker container every push to master we fear that they might spam to much containers.

For our project we are only needing the latest image with a tag. older images could be deleted.
We though that “Cleanup policy for tags is disabled” in Settings -> CI is the right place to setup such a image cleanup.
However this is disabled and only the administrator can enable it.

As there exists a issue: https://gitlab.com/gitlab-org/gitlab/-/issues/196124
my guess is, we are disabled because the repo is “to old” while newer repos are enabled?
Can this be confirmed?

If you guys want to save some GB storage we are happy to setup some cleanup policy if you enable it for the veloren group :slight_smile:

Have a nice day and continue your awesome work!

@xMAC94x Welcome to the GitLab Community Forum! :tada:

We very much appreciate the kind words! You’re pretty much right on the money. Our documentation on the container registration expiration policy goes a bit more in depth but essentially, if that project was created prior to the release of GitLab 12.8 then the policy won’t be enabled on it, and can’t be.

The issue you linked is where we’re tracking our efforts to get this enabled across the board on GitLab.com though, which is definitely in the works. The milestone assigned to that issue is currently set to 13.4 which correlates to the version of GitLab in which we’re expecting this change to be rolled out.

1 Like