search

greenkeeperio / greenkeeper-lockfile

:lock: Your lockfile, up to date, all the time
https://greenkeeper.io
183 stars 73 forks source link

Frequent yarn errors seen while installing greenkeeper-lockfile #109

Open rsimha opened 6 years ago

rsimha commented 6 years ago

This is breaking several CI builds and preventing other tests from being run.

For example, https://travis-ci.org/ampproject/amphtml/jobs/337372959#L1575

Error logs:

30.66s$ yarn global add greenkeeper-lockfile@1
yarn global v1.3.2
[1/4] Resolving packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/greenkeeper-lockfile: ETIMEDOUT".
info If you think this is a bug, please open a bug report with the information provided in "/home/travis/.config/yarn/global/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/global for documentation about this command.
The command "yarn global add greenkeeper-lockfile@1" failed and exited with 1 during .
rsimha commented 6 years ago

/cc @janl

Realtin commented 6 years ago

Hey,

a possible solution could be to add greenkeeper-lockfile to your devDependencies instead of installing it at the begin of the CI run. And then call the update/upload script from the node modules like this: ./node_modules/.bin/greenkeeper-lockfile-update

I had this setup in a test repo: https://github.com/Realtin/gk-test/commit/bb0f69a51aec5e2f458029117db6d4bdd603a1da#diff-1d37e48f9ceff6d8030570cd36286a61

LasaleFamine commented 6 years ago

I'm having this problem on Travis, is it like a regression?

Latest build: https://travis-ci.org/PolymerX/polymerx-cli/builds/383953242