|
|
|
|
|
by shinya
2840 days ago
|
|
> - IF YOU USE THE BUILT IN CACHE, parallelism will be hard (you cannot populate part of the cache from a job, another part from another job and in the next step use the result of both cache) You can use the `artifacts` and `dependencies` combo to leverage which artifact will be downloaded into a particular job. For instance, bundle-install:
stage: build
script: ...
artifacts:
paths: [bin/*]
yarn-install:
stage: build
script: ...
artifacts:
paths: [bin/*]
rspec:
stage: test
script: ...
dependencies: [bundle-install] # This downloads only `bundle-install` artifact to this job
karma:
stage: test
script: ...
dependencies: [yarn-install] # This downloads only `yarn-install` artifact to this job
eslint:
stage: test
script: ...
dependencies: [] # This downloads nothing
https://docs.gitlab.com/ee/ci/yaml/#dependencies explains how it works |
|