kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

Add image for clearing the cache docs

Browse source 
Closes https://gitlab.com/gitlab-org/gitlab-ee/issues/4642
This commit is contained in:
Achilleas Pipinellis 2018-03-22 13:16:47 +01:00
parent 89de9bd8bc
commit fade3e2451
No known key found for this signature in database
GPG key ID: A0996FBD3E92C17B
2 changed files with 10 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

BIN
doc/ci/caching/img/clear_runners_cache.png Normal file
View file

Binary file not shown.
Side by side

After

Width:  |  Height:  |  Size: 16 KiB

18
doc/ci/caching/index.md
View file

@ -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