Skip to content

Feature Request: Increase Generic Package Registry Size Limit on GitLab.com

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Feature Request: Increase Generic Package Registry Size Limit on GitLab.com

Problem Statement

The customer has a Business Unit that builds Windows VMs (10-12GB) using Packer in GitLab CI for product development and testing. Currently, these VMs are stored in the GitLab Generic Package Registry on their self-hosted instance (customer-dep.com), which uses S3 backend storage that supports files over 10GB.

The issue is that GitLab.com has a significantly lower size limit on their Package Registry:

  • Current documented Generic Package size limit: 5GB
  • Customer's required size: 10-12GB per VM package

This limitation is preventing migration of the customer's CI/CD workflows to GitLab.com.

Impact

  • Customer cannot migrate existing VM build pipelines to GitLab.com
  • The customer's team has already maximized compression on VMs and cannot reduce them below 10GB
  • Customer requires maintaining a separate infrastructure for hosting these artifacts

Customer Information

  • Customer SFDC Link
  • Use case: Windows VM builds using Packer in GitLab CI for product development and testing

Proposed Solution

Increase the maximum file size limit for the Generic Package Registry on GitLab.com to at least 12GB to accommodate the customer's VM packages.

Business Value

  • Enables migration of all the customer's CI/CD workflows to GitLab.com
  • Reduces the customer's infrastructure maintenance costs by eliminating need for separate artifact storage
  • Improves developer experience by keeping all artifacts within the same platform
  • Aligns with other customers' needs (referenced ModelOps team also evaluating 10GB limit)

Additional Context

Requested By

CSM - @guillene

Priority

High - This is a blocker for the customer's migration to GitLab.com

Edited by 🤖 GitLab Bot 🤖