Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use yarn install --frozen-lockfile in CI #1676

Merged
merged 3 commits into from
Apr 17, 2019
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 10 additions & 4 deletions .travis.yml
Original file line number Diff line number Diff line change
Expand Up @@ -8,11 +8,17 @@ env:
global:
- CXX=g++-4.8
before_install:
# Yarn defaults to an old version, make sure we
# get an up to date version
- npm install -g [email protected]
# Yarn defaults to an old version, make sure we get an up to date version
- npm install -g [email protected]
- '[ "${NPM_TOKEN+x}" ] && echo "//registry.npmjs.org/:_authToken=\${NPM_TOKEN}" > $HOME/.npmrc || echo "Skipping .npmrc creation";'

install:
# --frozen-lockfile doesn’t generate a yarn.lock lockfile and should fail if an update is needed.
# This will make sure that yarn.lock file in the PR is consistent with package.json.
#
# Due to a yarn issue (https://github.com/yarnpkg/yarn/issues/5840), --frozen-lockfile doesn't
# actually fail if an update is required, but integrity check from tools/pretest.js will catch
# the issue, so it still works as expected.
- yarn install --frozen-lockfile
before_script:
- cp config/ci.config.json config/project.json
- yarn build
Expand Down