Configurable CI components limit per project

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

  • Close this issue

Summary

Currently, the COMPONENTS_LIMIT is hardcoded in the codebase. We can make this limit configurable to provide more flexibility for different GitLab installations.

Proposed Solution

Make the components limit configurable through either:

  1. An environment variable (similar to GITLAB_CI_CONFIG_FETCH_TIMEOUT_SECONDS)
  2. An application limit in the instance settings

References

  • Current hardcoded limit: https://gitlab.com/gitlab-org/gitlab/-/blob/881cd96cd16fcee0078b5e61e5092b9cdcb6e4d6/app/models/ci/catalog/components_project.rb#L11
  • Environment variables documentation: https://docs.gitlab.com/administration/environment_variables/#supported-environment-variables
  • Application limits documentation: https://docs.gitlab.com/administration/instance_limits/
Edited Jul 08, 2025 by 🤖 GitLab Bot 🤖
Assignee Loading
Time tracking Loading