realaravinth/debian-mirror-gitlab
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
debian-mirror-gitlab/doc/user/admin_area/settings/continuous_integration.md
Pirate Praveen e0c922f897 New upstream version 11.5.3+dfsg
2018-12-13 13:39:08 +05:30

3.1 KiB
Raw Blame History

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.

Admin area settings button

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][art-yml] can be set in the Admin area of your GitLab instance. The value is in MB and the default is 100MB per job; on GitLab.com it's set to 1G.

To change it:

  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.

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.

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.