Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Léo-Paul Géneau
gitlab-ce
Commits
fade3e24
Commit
fade3e24
authored
Mar 22, 2018
by
Achilleas Pipinellis
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add image for clearing the cache docs
Closes
https://gitlab.com/gitlab-org/gitlab-ee/issues/4642
parent
89de9bd8
Changes
2
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
10 additions
and
8 deletions
+10
-8
doc/ci/caching/img/clear_runners_cache.png
doc/ci/caching/img/clear_runners_cache.png
+0
-0
doc/ci/caching/index.md
doc/ci/caching/index.md
+10
-8
No files found.
doc/ci/caching/img/clear_runners_cache.png
0 → 100644
View file @
fade3e24
15.7 KB
doc/ci/caching/index.md
View file @
fade3e24
...
...
@@ -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
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment