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
1
Merge Requests
1
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
nexedi
gitlab-ce
Commits
38a30ba4
Commit
38a30ba4
authored
Oct 16, 2019
by
Evan Read
Browse files
Options
Browse Files
Download
Plain Diff
Merge branch 'patch-35' into 'master'
Update index.md See merge request gitlab-org/gitlab!18625
parents
74ed9068
bb0667ec
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
3 additions
and
3 deletions
+3
-3
doc/ci/caching/index.md
doc/ci/caching/index.md
+3
-3
No files found.
doc/ci/caching/index.md
View file @
38a30ba4
...
...
@@ -491,8 +491,8 @@ job B:
To fix that, use different
`keys`
for each job.
In another case, let's assume you have more than one Runners assigned to your
project, but the distributed cache is not enabled.
We want t
he second time the
pipeline is run,
`job A`
and
`job B`
to re-use their cache (which in this case
project, but the distributed cache is not enabled.
T
he second time the
pipeline is run,
we want
`job A`
and
`job B`
to re-use their cache (which in this case
will be different):
```
yaml
...
...
@@ -518,7 +518,7 @@ job B:
```
In that case, even if the
`key`
is different (no fear of overwriting), you
might experience th
e cached files to
"get cleaned" before each stage if the
might experience th
at the cached files
"get cleaned" before each stage if the
jobs run on different Runners in the subsequent pipelines.
## Clearing the cache
...
...
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