From 77688b27369614fcec9216f440497402a9fbd8bd Mon Sep 17 00:00:00 2001 From: Marceli Wac Date: Tue, 11 Dec 2018 14:41:08 +0000 Subject: [PATCH] Patch 35 --- doc/ci/caching/index.md | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/doc/ci/caching/index.md b/doc/ci/caching/index.md index 758ab37861b..f93ccc4e3c1 100644 --- a/doc/ci/caching/index.md +++ b/doc/ci/caching/index.md @@ -29,8 +29,8 @@ needed to compile the project: Cache was designed to be used to speed up invocations of subsequent runs of a given job, by keeping things like dependencies (e.g., npm packages, Go vendor packages, etc.) so they don't have to be re-fetched from the public internet. - While the cache can be abused to pass intermediate build results between stages, - there may be cases where artifacts are a better fit. + While the cache can be abused to pass intermediate build results between + stages, there may be cases where artifacts are a better fit. - `artifacts`: **Use for stage results that will be passed between stages.** Artifacts were designed to upload some compiled/generated bits of the build, and they can be fetched by any number of concurrent Runners. They are @@ -39,11 +39,13 @@ needed to compile the project: directories relative to the build directory** and specifying paths which don't comply to this rule trigger an unintuitive and illogical error message (an enhancement is discussed at - https://gitlab.com/gitlab-org/gitlab-ce/issues/15530). Artifacts need to be - uploaded to the GitLab instance (not only the GitLab runner) before the next - stage job(s) can start, so you need to evaluate carefully whether your - bandwidth allows you to profit from parallelization with stages and shared - artifacts before investing time in changes to the setup. + [https://gitlab.com/gitlab-org/gitlab-ce/issues/15530](https://gitlab.com/gitlab-org/gitlab-ce/issues/15530) + ). Artifacts need to be uploaded to the GitLab instance (not only the GitLab + runner) before the next stage job(s) can start, so you need to evaluate + carefully whether your bandwidth allows you to profit from parallelization + with stages and shared artifacts before investing time in changes to the + setup. + It's sometimes confusing because the name artifact sounds like something that is only useful outside of the job, like for downloading a final image. But