Skip to content
GitLab

Variables

Variables store information, like passwords and secret keys, that you can use in job scripts. All projects on the instance can use these variables. Learn more.

Variables can be:

  • Protected: Only exposed to protected branches or protected tags.
  • Masked: Hidden in job logs. Must match masking requirements. Learn more.

Environment variables on this GitLab instance are configured to be protected by default.

Continuous Integration and Deployment

Customize CI/CD settings, including Auto DevOps, shared runners, and job artifacts.

The default domain to use for Auto Review Apps and Auto Deploy stages in all projects. Learn more.
Add a custom message with details about the instance's shared runners. The message is visible when you view runners for projects and groups. Markdown is supported.
The maximum file size for job artifacts. Learn more.
Set the default expiration time for job artifacts in all projects. Set to 0 to never expire artifacts by default. If no unit is written, it defaults to seconds. For example, these are all equivalent: 3600, 60 minutes, or one hour. Learn more.
Jobs older than the configured time are considered expired and are archived. Archived jobs can no longer be retried. Leave empty to never archive jobs automatically. The default unit is in days, but you can use other units, for example 15 days, 1 month, 2 years. Minimum value is 1 day. Learn more.

The default CI/CD configuration file and path for new projects.

CI/CD limits

Set limit to 0 to disable it.

Package Registry

Control how the GitLab Package Registry functions.

Package file size limits

Set limit to 0 to allow any file size.