Skip to content

G
gitlab-ce
Commit 6918dbc1 authored by Nourdin el Bacha's avatar Nourdin el Bacha
Browse files
Options

Remove duplicate paragraph regarding caching key

parent 2c6bce38
Hide whitespace changes
Inline Side-by-side
Showing with 0 additions and 4 deletions
doc/ci/yaml/README.md
View file @ 6918dbc1
...@@ -2774,10 +2774,6 @@ Otherwise cache content can be overwritten. ...@@ -2774,10 +2774,6 @@ Otherwise cache content can be overwritten.
> Introduced in GitLab Runner v1.0.0. > Introduced in GitLab Runner v1.0.0.
The cache is shared between jobs, so if you're using different
paths for different jobs, you should also set a different `cache:key`.
Otherwise cache content can be overwritten.
The `key` keyword defines the affinity of caching between jobs. The `key` keyword defines the affinity of caching between jobs.
You can have a single cache for all jobs, cache per-job, cache per-branch, You can have a single cache for all jobs, cache per-job, cache per-branch,
or any other way that fits your workflow. This way, you can fine tune caching, or any other way that fits your workflow. This way, you can fine tune caching,
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7