summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorMarcia Ramos <virtua.creative@gmail.com>2018-03-07 15:09:40 +0000
committerMarcia Ramos <virtua.creative@gmail.com>2018-03-07 15:09:40 +0000
commitd9ca76559f740bdeac78bcd9a7cfe60df5ef9795 (patch)
treeba5fa3be257f5e04df458a3210f8dedb48f7ab69 /doc
parentd282ea8976bf162a2e3c6344a5e33468cd62d00a (diff)
parent3d61a45b5dee8c943f350e7d8604d01d834cbf25 (diff)
downloadgitlab-ce-d9ca76559f740bdeac78bcd9a7cfe60df5ef9795.tar.gz
Merge branch 'docs/runner-cache-no-gc' into 'master'
Remove wrong assumption about Runners cache GC See merge request gitlab-org/gitlab-ce!17598
Diffstat (limited to 'doc')
-rw-r--r--doc/ci/runners/README.md3
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