... | ... | @@ -466,13 +466,14 @@ https://docs.gitlab.com/ee/raketasks/cleanup.html#remove-unreferenced-lfs-files |
|
|
[Delete old builds and artifacts](https://docs.gitlab.com/17.6/ee/administration/cicd/job_artifacts_troubleshooting.html?tab=Linux+package+%28Omnibus%29#delete-old-builds-and-artifacts)
|
|
|
[Delete old pipelines](https://docs.gitlab.com/17.6/ee/administration/cicd/job_artifacts_troubleshooting.html?tab=Linux+package+%28Omnibus%29#delete-old-pipelines)
|
|
|
|
|
|
### How do I clean the pipelines (artifacts, logs) ?
|
|
|
### How do I clean the pipelines (logs, artifacts) ?
|
|
|
|
|
|
In the course of time the size of data generated for gitlab-ci pipelines may grow quickly and sometimes reaches dozens of GB. The quantity of data stored on the gitlab's server for pipelines can be checked in the Settings -\> Usage Quotas panel of the project, or in Build -\> Artifacts. For projects with more than 10GB of artifacts there is certainly something to do to reduce the disk storage:
|
|
|
|
|
|
1) By cleaning old artifacts (cf https://gitlab.inria.fr/siteadmin/doc/-/wikis/faq#how-do-i-delete-the-oldest-or-most-recent-artifacts).
|
|
|
2) By disabling the "Keep artifacts from most recent successful jobs" in the Settings -\> CI/CD -\> Artifacts if not necessary because it keeps all job's artifacts (build, test, etc) of all the git refs (branches, tags, merge requests, ...) and this can cost a lot.
|
|
|
3) By changing the gitlab-ci jobs definitions, for example:
|
|
|
1) From GitLab version 17.9, it is possible to [set automatic deletion of old continuous integration pipelines](https://docs.gitlab.com/ci/pipelines/settings/#automatic-pipeline-cleanup).
|
|
|
2) By cleaning old artifacts (cf https://gitlab.inria.fr/siteadmin/doc/-/wikis/faq#how-do-i-delete-the-oldest-or-most-recent-artifacts).
|
|
|
3) By disabling the "Keep artifacts from most recent successful jobs" in the Settings -\> CI/CD -\> Artifacts if not necessary because it keeps all job's artifacts (build, test, etc) of all the git refs (branches, tags, merge requests, ...) and this can cost a lot.
|
|
|
4) By changing the gitlab-ci jobs definitions, for example:
|
|
|
- use the [expire_in](https://docs.gitlab.com/ee/ci/yaml/#artifactsexpire_in) keyword to reduce the expiration time (30 days by default) of artifacts,
|
|
|
- use [cache](https://docs.gitlab.com/ee/ci/yaml/#cache) instead of artifacts when possible when jobs with dependencies can be executed on the same machine,
|
|
|
- generate fewer archives and lighter archives, keeping only what is strictly necessary.
|
... | ... | |