"permission denied" errors with CircleCI

[sheelah]

I'm getting /bin/bash: /usr/local/bin/greenkeeper-lockfile-update: Permission denied Exited with code 1 errors under CircleCI 2.0 during the workflow step where Greenkeeper should be updating package-lock.json.

The relevant steps in my build workflow are: sudo npm i -g greenkeeper-lockfile@1: works fine greenkeeper-lockfile-update && greenkeeper-lockfile-upload: permission denied errors

I verified that GH_TOKEN is available in my project's CircleCI environment variables, which is set to a Github personal access token that has full repo permissions. Is there something else I need to do to get this working?

Thanks!

[Xiphe]

im seeing this, too. It's really flaky though - though it was caused by circle cache but seems to not be the case since you're reinstalling greenkeeper lockfile on every run...

I'll post a failing build once it happens again

[branoholy]

I have the same problem but it seems like it's not related to greenkeeper-lockfile. The same problem occurs with any package installed globally with sudo npm i -g. It's interesting it doesn't happen every time.

[Xiphe]

In my case I have greenkeeper-lockfile installed as a devDependency of my project and execute it via $(npm bin)/greenkeeper-lockfile. No sudo, same error

[Xiphe]

I also have this error with other npm binaries, so I suspect It's a circle error and not caused by greenkeeper-lockfile

[janl]

Thanks for reporting. Please reopen this issue, if you see this again, and if you have any pointers as to how greenkeeper-lockfile is involved :)