summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorStan Hu <stanhu@gmail.com>2015-12-11 23:40:58 -0800
committerStan Hu <stanhu@gmail.com>2015-12-11 23:40:58 -0800
commite8d35ea149f1d40768d99835c30d40e4028953f0 (patch)
treed934c4e1ecbed7f093d5313027e0923ecbac33a5
parent885bfe3bdc40ffa927fadb54cd0afb3587c1d5c9 (diff)
parent7dfbf7cf55e5e96986eca8711bfdd92956c09498 (diff)
downloadgitlab-ce-e8d35ea149f1d40768d99835c30d40e4028953f0.tar.gz
Merge branch 'master' of gitlab.com:gitlab-org/gitlab-ce
-rw-r--r--doc/ci/yaml/README.md3
1 files changed, 3 insertions, 0 deletions
diff --git a/doc/ci/yaml/README.md b/doc/ci/yaml/README.md
index 3dbf1afc7a9..7e2edb945da 100644
--- a/doc/ci/yaml/README.md
+++ b/doc/ci/yaml/README.md
@@ -113,6 +113,9 @@ The YAML-defined variables are also set to all created service containers, thus
### cache
`cache` is used to specify list of files and directories which should be cached between builds.
+Caches are stored according to the branch/ref and the job name. Caches are not
+currently shared between different job names or between branches/refs. This means
+caching will benefit you if you push subsequent commits to an existing feature branch.
**The global setting allows to specify default cached files for all jobs.**