Programmatically delete duplicate package assets.
Purpose of this issue
I'd like to have a targeted discussion of the UX of the MVC of package cleanup policies - specifically cleanup package files. I would like to leave #227233 (closed) as the future vision issue. I'm not sure if this is the right process, so please correct me if I'm wrong.
Customer problem
As discovered in problem validation, customers want a way to manage storage used by snapshots and pre-releases. In GitLab, when a customer is working on a snapshot, they will re-upload a package with the same name and version to the registry. This essentially adds more files to an existing package in the registry. The more you update a package, the more files it accumulates, the more storage it will take.
From problem validation:
One participant has majority Maven packages. Per sprint of 3 weeks work they work on a snapshot version; one snapshot can product 250 artifacts amounting to 13 gigs.
🔽
Design proposal - Attached to this issue.
- Figma
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.