summaryrefslogtreecommitdiff
path: root/doc/administration
diff options
context:
space:
mode:
authorGitLab Bot <gitlab-bot@gitlab.com>2021-09-01 03:11:03 +0000
committerGitLab Bot <gitlab-bot@gitlab.com>2021-09-01 03:11:03 +0000
commita3c1c29aa588228a2ae9c000620d1b73ff159fe3 (patch)
tree780805b1255c831569dfb1f43e1ac0f80917d8be /doc/administration
parent74dae34e98c5a321b152083022e7c210e875168c (diff)
downloadgitlab-ce-a3c1c29aa588228a2ae9c000620d1b73ff159fe3.tar.gz
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/administration')
-rw-r--r--doc/administration/instance_limits.md23
1 files changed, 23 insertions, 0 deletions
diff --git a/doc/administration/instance_limits.md b/doc/administration/instance_limits.md
index 6fb8d2ed80a..9765e6956ad 100644
--- a/doc/administration/instance_limits.md
+++ b/doc/administration/instance_limits.md
@@ -513,6 +513,29 @@ Update `ci_jobs_trace_size_limit` with the new value in megabytes:
Plan.default.actual_limits.update!(ci_jobs_trace_size_limit: 125)
```
+### Maximum size and depth of CI/CD configuration YAML files
+
+The default maximum size of a CI/CD configuration YAML file is 1 megabyte and the default depth is 100.
+
+You can change these limits in the [GitLab Rails console](operations/rails_console.md#starting-a-rails-console-session).
+Update `max_yaml_size_bytes` with the new value in megabytes:
+
+```ruby
+ApplicationSetting.update!(max_yaml_size_bytes: 2.megabytes)
+```
+
+Update `max_yaml_depth` with the new value in megabytes:
+
+```ruby
+ApplicationSetting.update!(max_yaml_depth: 125)
+```
+
+To disable this limitation entirely, disable the feature flag in the console:
+
+```ruby
+Feature.disable(:ci_yaml_limit_size)
+```
+
## Instance monitoring and metrics
### Limit inbound incident management alerts