我在我的CI中有一个setup作业，它安装所有npm软件包并将它们存储在缓存中:
setup:
stage: pre-build
cache:
untracked: true
when: on_success
key:
files:
- repo-hash
prefix: workspace
script:
- yarn install --frozen-lockfile
目前，如果在两个流水线之间，仓库哈希值没有改变，作业会成功下载现有的缓存，但仍然会运行yarn install --frozen-lockfile命令。
如何更改此行为，以便如果缓存存在，跳过该作业？
尝试退出？
install:
stage: install
cache:
key:
files:
- package-lock.json
prefix: $CI_PROJECT_NAME
paths:
- node_modules/
script:
- |
if [[ -d node_modules ]]; then
exit 10
fi
- npm ci --cache .npm --prefer-offline
allow_failure:
exit_codes: 10
目前在一个基于NPM的Preact项目中，我正在使用gitlab-ci.yml的only功能，如果package-lock.json有任何更改，就运行安装作业（如果没有更改，则跳过安装）。然后我的构建作业从安装作业中获取node_modules缓存：
install:
stage: setup # gitlab.com shared runners are slow; don't run unless there's a reason to install
cache: # even a "echo 'hello world'" script would be about a 30s job, worse if queued
key:
files: [package-lock.json] # the key is a hash of package-lock; branches with it will use this cache :D
paths: [node_modules] # we're not caching npm (ie `npm ci --prefer-offline --cache`) because it's slow
policy: push # override the default behavior of wasting time downloading and unpacking node_modules
script: [npm ci] # I believe in package-lock/npm ci's mission
only:
changes: [package-lock.json] # our forementioned reason to install
refs:
- master
- develop
- merge_requests
build: # uses the default behavior, which runs even if install is skipped; but not if install failed
stage: build
cache:
key:
files: [package-lock.json]
paths: [node_modules]
policy: pull # override the default behavior of wasting time packing and uploading node_modules
script:
- npm run build
artifacts:
paths: [build]
only:
changes:
- src/**/*
- tsconfig.json
- preact.config.js
- package-lock.json
refs:
- master
- develop
- merge_requests
对于Yarn，您只需使用yarn.lock替换此处看到的任何package-lock.json，并用yarn install --frozen-lockfile替换npm ci。
以前，我是这样做的（类似于这里其他答案中的一个）：
build:
stage: build
cache:
key:
files: [package-lock.json]
paths: [node_modules]
script:
- test -d node_modules || npm ci
- npm run build
artifacts:
paths: [build]
only:
changes:
- src/**/*
- tsconfig.json
- preact.config.js
- package-lock.json
refs:
- master
- develop
- merge_requests
stages:
- setup
- test
- build
- release
- publish
cache: &dependency-cache
key:
files:
- "**/yarn.lock"
paths:
- node_modules
- "*/node_modules"
policy: pull
renew-cache:
stage: setup
except:
- /master.*/
- tags
script:
- test -d node_modules || yarn && yarn workspace app ngcc --properties es2015 browser module main
cache:
<<: *dependency-cache
policy: pull-push
test-app:
stage: test
except:
- /master.*/
- tags
script:
- test -d node_modules || yarn
- yarn workspace app test
build-app:
stage: build
only:
- /master.*/
script:
- test -d node_modules || yarn
- yarn workspace app build
# Store build results ...
# The rest of the pipeline
node-modules yarn链接器和dependency模块提升限制pull策略，renew-cache作业是唯一可以写入缓存的作业test -d node_modules || <COMMAND>仅在未找到node_modules目录时运行<COMMAND> - 作业无缓存yarn.lock被修改时才推送新缓存yarn.lock文件未更改node_modules测试 - 缓存可能已过期，流水线必须确定性可重复这种方法并不能完全消除每次运行设置作业的需要，因此仍然存在一些开销。但是，整个流水线的运行时间大大减少。
希望这能有所帮助 :-)
.yarn目录，例如 https://classic.yarnpkg.com/en/docs/install-ci/；你仍然需要进行安装，但是大多数（如果不是全部）文件已经在本地了。 - jonrsharpeyarn install步骤:/ - Nicoowrchanges关键字，仅在指定字段更改时运行作业：https://docs.gitlab.com/ee/ci/yaml/#ruleschanges - Nicoowr