From 7c9cff3a744a64848207bfde1aedcfe652f07dce Mon Sep 17 00:00:00 2001 From: Lin Jen-Shin Date: Mon, 6 Mar 2017 19:20:28 +0800 Subject: Update for document feedback: * https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/9666#note_24829863 * https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/9666#note_24829880 * https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/9666#note_24830028 --- doc/ci/yaml/README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/ci/yaml/README.md b/doc/ci/yaml/README.md index 221515e4457..f4224496207 100644 --- a/doc/ci/yaml/README.md +++ b/doc/ci/yaml/README.md @@ -166,8 +166,8 @@ which can be set in GitLab's UI. cached between jobs. You can only use paths that are within the project workspace. -**By default caching is enabled and shared between each pipelines and -each jobs, starting from GitLab 9.0** +**By default caching is enabled and shared between pipelines and jobs, +starting from GitLab 9.0** If `cache` is defined outside the scope of jobs, it means it is set globally and all jobs will use that definition. @@ -219,9 +219,9 @@ rspec: - binaries/ ``` -Note that since cache is shared between each jobs, if you're using different +Note that since cache is shared between jobs, if you're using different paths for different jobs, you should also set a different *cache:key* -otherwise they could be overwriting to each other. +otherwise cache content can be overwritten. The cache is provided on a best-effort basis, so don't expect that the cache will be always present. For implementation details, please check GitLab Runner. -- cgit v1.2.1