Backend: Increase the default for .gitlab-ci.yml's Parsed YAML Size Limit
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Release notes
Problem to solve
Today gitlab parsed size limitation is hardcoded to 1 Megabyte for the max_size and 100 for the max_depth, and some users are hitting this limitation. When that happens they have to restructure their config in attempt to reduce its size, or change the limit manually. In !68593 (diffs) (#30098 (comment 1052733939)+) we made it possible to change the limit using the rails console, however we should also look into whether we could safely increase the limit so more users with legitimate config can operate without having to adjust the limit on the console.
Update: The limit was raised to 2MB and 150 max depth as part of #473777 (closed)
Proposal
Consider increasing the default size limit for CI yaml.
Additional notes
In !91268 (closed) the ci_yaml_limit_size feature flag was dropped, so any instance that has the flag disabled will need to update the limits to a more suitable value.
Intended users
Feature Usage Metrics
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.