kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity

Merge branch 'patch-35' into 'master'

Browse source 
Patch 35

See merge request gitlab-org/gitlab-ce!23711
This commit is contained in:
Achilleas Pipinellis 2018-12-11 14:41:09 +00:00
commit 56936cd898
1 changed files with 9 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
doc/ci/caching/index.md
View file

@ -29,8 +29,8 @@ needed to compile the project:
Cache was designed to be used to speed up invocations of subsequent runs of a 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 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. 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, While the cache can be abused to pass intermediate build results between
there may be cases where artifacts are a better fit. stages, there may be cases where artifacts are a better fit.
- `artifacts`: **Use for stage results that will be passed between stages.** - `artifacts`: **Use for stage results that will be passed between stages.**
Artifacts were designed to upload some compiled/generated bits of the build, 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 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 directories relative to the build directory** and specifying paths which don't
comply to this rule trigger an unintuitive and illogical error message (an comply to this rule trigger an unintuitive and illogical error message (an
enhancement is discussed at enhancement is discussed at
https://gitlab.com/gitlab-org/gitlab-ce/issues/15530). Artifacts need to be [https://gitlab.com/gitlab-org/gitlab-ce/issues/15530](https://gitlab.com/gitlab-org/gitlab-ce/issues/15530)
uploaded to the GitLab instance (not only the GitLab runner) before the next ). Artifacts need to be uploaded to the GitLab instance (not only the GitLab
stage job(s) can start, so you need to evaluate carefully whether your runner) before the next stage job(s) can start, so you need to evaluate
bandwidth allows you to profit from parallelization with stages and shared carefully whether your bandwidth allows you to profit from parallelization
artifacts before investing time in changes to the setup. 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 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 is only useful outside of the job, like for downloading a final image. But