diff options
author | Achilleas Pipinellis <axil@gitlab.com> | 2018-03-07 13:16:27 +0100 |
---|---|---|
committer | Achilleas Pipinellis <axil@gitlab.com> | 2018-03-07 13:16:27 +0100 |
commit | 3d61a45b5dee8c943f350e7d8604d01d834cbf25 (patch) | |
tree | 5919f4a3f935ebd6bdc47865df8477f2f99c940b | |
parent | 95016507d49c3099afde0ef3909377bf70061dc3 (diff) | |
download | gitlab-ce-docs/runner-cache-no-gc.tar.gz |
Remove wrong assumption about Runners cache GCdocs/runner-cache-no-gc
https://gitlab.com/gitlab-org/gitlab-ce/issues/41249#note_60629323
-rw-r--r-- | doc/ci/runners/README.md | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/ci/runners/README.md b/doc/ci/runners/README.md index 03aa6ff8e7c..f879ed62010 100644 --- a/doc/ci/runners/README.md +++ b/doc/ci/runners/README.md @@ -163,8 +163,7 @@ in your `.gitlab-ci.yml`. Behind the scenes, this works by increasing a counter in the database, and the value of that counter is used to create the key for the cache. After a push, a -new key is generated and the old cache is not valid anymore. Eventually, the -Runner's garbage collector will remove it form the filesystem. +new key is generated and the old cache is not valid anymore. ## How shared Runners pick jobs |