## Problem The label "**Maximum artifacts archive size (bytes)**" in Admin > Settings > CI/CD > Continuous Integration and Deployment is unclear and doesn't accurately describe what the setting does. Additionally, the related documentation lacks information about accessing and configuring this setting through the admin interface. ## Current Behavior - The UI label is "Maximum artifacts archive size (bytes)" - The setting name is `max_artifacts_content_include_size` - Users may confuse this with "Maximum artifacts size (MB)" which controls job artifact uploads - The documentation only shows how to change the setting via Rails console, not through the admin UI ## What It Actually Does This setting controls the **maximum size of artifact files when they're extracted and read** for inclusion in CI/CD configurations (specifically for dynamic child pipelines). It does NOT control the size of the artifact archive itself during upload. ## Issues to Address ### 1. UI Label Clarity The label should be more descriptive, such as: - "Maximum artifact file size for pipeline includes (bytes)" - "Maximum artifact content size for dynamic child pipelines (bytes)" - Or add help text explaining the actual functionality ### 2. Documentation Gap The documentation at https://docs.gitlab.com/administration/instance_limits/#maximum-size-of-the-ci-artifacts-archive currently only shows: ``ApplicationSetting.update(max_artifacts_content_include_size: 20.megabytes)`` ## Screenshots or screen recordings {width=900 height=600} ## How to access the setting in the admin UI Visit Admin > Settings > CI/CD > Expand Continuous Integration and Deployment ## Related - MR: !166496 (introduced this UI setting) - MR: !148554 (introduced the underlying feature) - Issue: #455191 - Documentation: https://docs.gitlab.com/administration/instance_limits/#maximum-size-of-the-ci-artifacts-archive