diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2020-06-11 06:08:30 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2020-06-11 06:08:30 +0300 |
| commit | 7b0ffedd699f02990b1af3e6d84f914cb72659b1 (patch) | |
| tree | 77419232f9954bb83792384432a2a50ee6d62402 /doc/ci/caching/index.md | |
| parent | 4cdbecb46571861c20908aa6b1dda684f6baf76b (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/ci/caching/index.md')
| -rw-r--r-- | doc/ci/caching/index.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/ci/caching/index.md b/doc/ci/caching/index.md index a9ca38e195d..392dd4fdeba 100644 --- a/doc/ci/caching/index.md +++ b/doc/ci/caching/index.md @@ -86,9 +86,9 @@ which type of Runner you are using, cache can act differently. From the perspective of the developer, to ensure maximum availability of the cache, when declaring `cache` in your jobs, use one or a mix of the following: -- [Tag your Runners](../runners/README.md#using-tags) and use the tag on jobs +- [Tag your Runners](../runners/README.md#use-tags-to-limit-the-number-of-jobs-using-the-runner) and use the tag on jobs that share their cache. -- [Use sticky Runners](../runners/README.md#locking-a-specific-runner-from-being-enabled-for-other-projects) +- [Use sticky Runners](../runners/README.md#prevent-a-specific-runner-from-being-enabled-for-other-projects) that will be only available to a particular project. - [Use a `key`](../yaml/README.md#cachekey) that fits your workflow (for example, different caches on each branch). For that, you can take advantage of the |