Enable pipeline hierarchy size limit by default
Four Merge Requests to address https://gitlab.com/gitlab-org/gitlab/-/issues/358075
Rollout issue: #373719 (closed)
| Step | Merge Request | |
|---|---|---|
| 1 | !95753 (merged) Rename pipeline hierarchy methods | |
| 2 | !95756 (merged) Report full size of Ci::Pipeline hierarchy trees | |
| 3 | !95857 (merged) Broadly restrict downstream pipeline tree size | |
| 4 | !97841 (merged) Enable pipeline hierarchy size limit by default #375277 (closed) |
|
What does this MR do and why?
This MR enables (by default) the pipeline hierarchy size restriction we introduced in !95857 (merged)
At this point, we'll have watched the reporting from !95756 (merged) for awhile to validate that introducing a limit of 1000 won't be disruptive on GitLab SaaS. Once we know that's okay for us, we'll turn it on for SaaS and eanble it by default in %15.4 to lead with stable-by-default and let instance administrators opt-out if they have a problem.
We also may choose to use a lower limit than 500 depending on what we see in !95756 (merged)
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by drew stachon