summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorNick Thomas <nick@gitlab.com>2016-10-14 15:53:06 +0100
committerNick Thomas <nick@gitlab.com>2016-10-14 15:53:06 +0100
commit3f8fa3576509e2c90fbf9c18450e3daede32deac (patch)
tree71a11a9fbe965b7b198d5406f37eee51d6044b7e /doc
parentd64a9fb079de92e90cf8c0665ce85ee3251f3443 (diff)
downloadgitlab-ce-3f8fa3576509e2c90fbf9c18450e3daede32deac.tar.gz
Document restrictions on cache and artifact paths
See https://gitlab.com/gitlab-org/gitlab-ci-multi-runner/issues/1792
Diffstat (limited to 'doc')
-rw-r--r--doc/ci/yaml/README.md7
1 files changed, 4 insertions, 3 deletions
diff --git a/doc/ci/yaml/README.md b/doc/ci/yaml/README.md
index 59399861a97..84ea59ab687 100644
--- a/doc/ci/yaml/README.md
+++ b/doc/ci/yaml/README.md
@@ -159,7 +159,8 @@ Variables can be also defined on [job level](#job-variables).
> Introduced in GitLab Runner v0.7.0.
`cache` is used to specify a list of files and directories which should be
-cached between builds.
+cached between builds. You can only use paths that are within the project
+workspace.
**By default the caching is enabled per-job and per-branch.**
@@ -606,8 +607,8 @@ You can see a simple example at https://gitlab.com/gitlab-examples/review-apps-n
> - Build artifacts are only collected for successful builds by default.
`artifacts` is used to specify a list of files and directories which should be
-attached to the build after success. To pass artifacts between different builds,
-see [dependencies](#dependencies).
+attached to the build after success. You can only use paths that are within the
+project workspace. To pass artifacts between different builds, see [dependencies](#dependencies).
Below are some examples.