Project gitlab-org/gitlab CI yaml file size approaching instance sizing limit
Problem Statement
By default, the size limit allotted for the GitLab CI config file is 1MB. With the recent upgrade to version 3.2, the yaml file has grown to just shy over this. On our Dev instance, this causes issues as processing the CI file does not happen, instead pipelines come to a halt which creates blockers in various areas including Auto-Deployments and Releases. For some reason on SaaS, we're still below this limit it appears.
To resolve this on Dev, we bumped the limit to 2MB. If we add anything else to our CI configs, we'll need to make an instance wide change to .com to bump the size limitation. I would advise that we look into what has been added recently or if there's any cruft that could be removed to prevent such a drastic configuration change that impacts the scope of the entire .com environment.
Reference: gitlab-com/gl-infra/production#18314 (closed)
Solution
-
Increase
max_total_yaml_size
from1M
to1.2M
-
Add a db migration to update the default value for
max_yaml_size_bytes
to2M
as well