Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAchilleas Pipinellis <axil@gitlab.com>2018-03-22 15:16:47 +0300
committerAchilleas Pipinellis <axil@gitlab.com>2018-03-22 15:19:48 +0300
commitfade3e24514a0e3d86a65f71c0f2d282c6b3f328 (patch)
tree81a6625905859eb00b833e191e90b7c510234564 /doc/ci/caching/index.md
parent89de9bd8bc0ccdc814e68507b9f8a55350ebadc7 (diff)
Add image for clearing the cache docs
Closes https://gitlab.com/gitlab-org/gitlab-ee/issues/4642
Diffstat (limited to 'doc/ci/caching/index.md')
-rw-r--r--doc/ci/caching/index.md18
1 files changed, 10 insertions, 8 deletions
diff --git a/doc/ci/caching/index.md b/doc/ci/caching/index.md
index c4b2a25d4a8..c159198d16b 100644
--- a/doc/ci/caching/index.md
+++ b/doc/ci/caching/index.md
@@ -454,17 +454,19 @@ next run of the pipeline, the cache will be stored in a different location.
> [Introduced](https://gitlab.com/gitlab-org/gitlab-ce/issues/41249) in GitLab 10.4.
If you want to avoid editing `.gitlab-ci.yml`, you can easily clear the cache
-via GitLab's UI. This will have an impact on all caches of your project as
-name of the cache directory will be renamed by appending an integer to it
-(`-1`, `-2`, etc.):
+via GitLab's UI:
-1. Navigate to your project's **CI/CD > Pipelines** page.
-1. Click on the **Clear Runner caches** to clean up the cache.
-1. On the next push, your CI/CD job will use a new cache.
+1. Navigate to your project's **CI/CD > Pipelines** page
+1. Click on the **Clear Runner caches** button to clean up the cache
+
+ ![Clear Runners cache](img/clear_runners_cache.png)
+
+1. On the next push, your CI/CD job will use a new cache
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.
+value of that counter is used to create the key for the cache by appending an
+integer to it: `-1`, `-2`, etc. After a push, a new key is generated and the
+old cache is not valid anymore.
## Cache vs artifacts