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:
authorGitLab Bot <gitlab-bot@gitlab.com>2019-10-16 09:07:06 +0300
committerGitLab Bot <gitlab-bot@gitlab.com>2019-10-16 09:07:06 +0300
commit3546e1bb0971347e9e9984de0799e3fb53743b33 (patch)
treef65e47d5deb95905aa419ebd70ce02c7b32ddb8f /doc/ci/caching
parentf155cc9034f2247c5d368f9b0212ad44248b0c5e (diff)
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/ci/caching')
-rw-r--r--doc/ci/caching/index.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/ci/caching/index.md b/doc/ci/caching/index.md
index 6a7b60c2ba5..6b8e7fa2ad5 100644
--- a/doc/ci/caching/index.md
+++ b/doc/ci/caching/index.md
@@ -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 the 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. The 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 the cached files to "get cleaned" before each stage if the
+might experience that the cached files "get cleaned" before each stage if the
jobs run on different Runners in the subsequent pipelines.
## Clearing the cache