diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-10-17 12:12:03 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-10-17 12:12:03 +0300 |
| commit | 550096a3bf94b5d8e2b74dc8f94fbb0c579a7313 (patch) | |
| tree | ca0d548e9a1c369df1a07a60ef0a26503653e00e /doc/ci/caching | |
| parent | 600cd0747bbb2c1f089785572a159cce6c4ce806 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/ci/caching')
| -rw-r--r-- | doc/ci/caching/index.md | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/ci/caching/index.md b/doc/ci/caching/index.md index 15e8c617102..f690dd3ca24 100644 --- a/doc/ci/caching/index.md +++ b/doc/ci/caching/index.md @@ -57,7 +57,9 @@ For runners to work with caches efficiently, you must do one of the following: - Use multiple runners that have [distributed caching](https://docs.gitlab.com/runner/configuration/autoscale.html#distributed-runners-caching), where the cache is stored in S3 buckets. Shared runners on GitLab.com behave this way. These runners can be in autoscale mode, - but they don't have to be. + but they don't have to be. To manage cache objects, + apply lifecycle rules to delete the cache objects after a period of time. + Lifecycle rules are available on the object storage server. - Use multiple runners with the same architecture and have these runners share a common network-mounted directory to store the cache. This directory should use NFS or something similar. These runners must be in autoscale mode. |