debian-mirror-gitlab/doc/user/admin_area/settings/continuous_integration.md

type
reference

Continuous Integration and Deployment Admin settings (CORE ONLY)

In this area, you will find settings for Auto DevOps, Runners and job artifacts. You can find it in the admin area, under Settings > Continuous Integration and Deployment.

Auto DevOps (CORE ONLY)

To enable (or disable) Auto DevOps for all projects:

1. Go to Admin area > Settings > Continuous Integration and Deployment
2. Check (or uncheck to disable) the box that says "Default to Auto DevOps pipeline for all projects"
3. Optionally, set up the Auto DevOps base domain which is going to be used for Auto Deploy and Auto Review Apps.
4. Hit Save changes for the changes to take effect.

From now on, every existing project and newly created ones that don't have a .gitlab-ci.yml, will use the Auto DevOps pipelines.

If you want to disable it for a specific project, you can do so in its settings.

Maximum artifacts size (CORE ONLY)

The maximum size of the job artifacts can be set at:

• The instance level.
• From GitLab 12.4, the project and group level.

The value is:

• In MB and the default is 100MB per job.
• Set to 1G on GitLab.com.

To change it at the:

• Instance level:

  1. Go to Admin area > Settings > Continuous Integration and Deployment.
  2. Change the value of maximum artifacts size (in MB).
  3. Hit Save changes for the changes to take effect.

• Group level (this will override the instance setting):

  1. Go to the group's Settings > CI / CD > General Pipelines.
  2. Change the value of maximum artifacts size (in MB).
  3. Press Save changes for the changes to take effect.

• Project level (this will override the instance and group settings):

  1. Go to the project's Settings > CI / CD > General Pipelines.
  2. Change the value of maximum artifacts size (in MB).
  3. Press Save changes for the changes to take effect.

NOTE: Note The setting at all levels is only available to GitLab administrators.

Default artifacts expiration (CORE ONLY)

The default expiration time of the job artifacts can be set in the Admin area of your GitLab instance. The syntax of duration is described in artifacts:expire_in and the default value is 30 days. On GitLab.com they never expire.

1. Go to Admin area > Settings > Continuous Integration and Deployment.
2. Change the value of default expiration time.
3. Hit Save changes for the changes to take effect.

This setting is set per job and can be overridden in .gitlab-ci.yml. To disable the expiration, set it to 0. The default unit is in seconds.

Shared Runners pipeline minutes quota (STARTER ONLY)

Introduced in GitLab Starter 8.16.

If you have enabled shared Runners for your GitLab instance, you can limit their usage by setting a maximum number of pipeline minutes that a group can use on shared Runners per month. Setting this to 0 (default value) will grant unlimited pipeline minutes. While build limits are stored as minutes, the counting is done in seconds. Usage resets on the first day of each month. On GitLab.com, the quota is calculated based on your subscription plan.

To change the pipelines minutes quota:

1. Go to Admin area > Settings > Continuous Integration and Deployment
2. Set the pipeline minutes quota limit.
3. Hit Save changes for the changes to take effect

---

While the setting in the Admin area has a global effect, as an admin you can also change each group's pipeline minutes quota to override the global value.

1. Navigate to the Groups admin area and hit the Edit button for the group you wish to change the pipeline minutes quota.
2. Set the pipeline minutes quota to the desired value
3. Hit Save changes for the changes to take effect.

Once saved, you can see the build quota in the group admin view. The quota can also be viewed in the project admin view if shared Runners are enabled.

You can see an overview of the pipeline minutes quota of all projects of a group in the Usage Quotas page available to the group page settings list.

Archive jobs (CORE ONLY)

Archiving jobs is useful for reducing the CI/CD footprint on the system by removing some of the capabilities of the jobs (metadata needed to run the job), but persisting the traces and artifacts for auditing purposes.

To set the duration for which the jobs will be considered as old and expired:

1. Go to Admin area > Settings > CI/CD > Continuous Integration and Deployment.
2. Change the value of "Archive jobs".
3. Hit Save changes for the changes to take effect.

Once that time passes, the jobs will be archived and no longer able to be retried. Make it empty to never expire jobs. It has to be no less than 1 day, for example: 15 days, 1 month, 2 years.

Default CI configuration path

Introduced in GitLab 12.5.

The default CI configuration file path for new projects can be set in the Admin area of your GitLab instance (.gitlab-ci.yml if not set):

1. Go to Admin area > Settings > Continuous Integration and Deployment.
2. Input the new path in the Default CI configuration path field.
3. Hit Save changes for the changes to take effect.

It is also possible to specify a custom CI configuration path for a specific project.

Required pipeline configuration (PREMIUM ONLY)

CAUTION: Caution: The Required Pipeline Configuration feature is deprecated and will be removed when an improved compliance solution is added to GitLab. It is recommended to avoid using this feature.

GitLab administrators can force a pipeline configuration to run on every pipeline.

The configuration applies to all pipelines for a GitLab instance and is sourced from:

• The instance template repository.
• GitLab-supplied configuration.

To set required pipeline configuration:

1. Go to Admin area > Settings > CI/CD.
2. Expand the Required pipeline configuration section.
3. Select the required configuration from the provided dropdown.
4. Click Save changes.