diff options
| author | Achilleas Pipinellis <axilleas@axilleas.me> | 2015-12-12 01:10:23 +0300 |
|---|---|---|
| committer | Achilleas Pipinellis <axilleas@axilleas.me> | 2015-12-12 01:10:23 +0300 |
| commit | 7dfbf7cf55e5e96986eca8711bfdd92956c09498 (patch) | |
| tree | 1eaa8ba0583aa1dc50726b8d17f96925fbf1b0fa | |
| parent | 03a5df9974df4dc839107053e66994a11a358866 (diff) | |
| parent | baa97175abd25eb566d7273bc188a6459639abf3 (diff) | |
Merge branch 'clarify_ci_caching' into 'master'
Clarify cache behavior
After chatting with @ayufan about CI caching, I added some info to the documentation. This should make it clear how caching currently works.
cc/ @ayufan Is this accurate?
See merge request !2072
| -rw-r--r-- | doc/ci/yaml/README.md | 3 |
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.** |