Raise user-limit on DAG relationships
Problem to solve
We currently have a maximum of 10 on dependencies for a DAG, but there are common workflows where a higher limit than this is needed. We need to determine what the system protection limit is and set the maximum to that number rather than a number that users are bumping into.
We also want to provide a (potentially unsupported) very high limit for self-managed instance administrators who choose to do so.
See also infrastructure issue at https://gitlab.com/gitlab-com/gl-infra/infrastructure/-/issues/7541
Current limitations are documented at https://docs.gitlab.com/ee/ci/yaml/README.html#requirements-and-limitations
Note that majority of the efforts of this issue have been merged, please refer to: #197886 (comment 394376627) for the work remaining
Intended users
Further details
Proposal
- Update the DAG limit for normal operation to 50 users, and apply this feature flag in production.
- Set a "crazy" limit feature flag that allows for setting the limit to something like 1000, for instance administrators at their own risk. We have users who are running things at this level, so it isn't a footgun, but it is an untested configuration (officially) and helps teams who are doing so not to source patch GitLab. The actual number here is still TBD.
Permissions and Security
None new
Documentation
Availability & Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Links / references
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.