Not found binary in the DroneCI
See original GitHub issueCurrent behavior:
The code in DroneCI config
pipeline:
restore-cache:
image: drillster/drone-volume-cache
restore: true
mount:
- ./node_modules
- ~/.cache
- ~/.npm
volumes:
- /tmp/cache:/cache
ttl: 3
build:
image: getninjas/nodejs:9-chrome64
commands:
- npm ci
integration-test:
group: tests
image: getninjas/nodejs:9-chrome64
commands:
- npm run server:test
- ./node_modules/bin/cypress run
- npm run clear:pm2
environment:
- REDIS_HOST=redis
rebuild-cache:
image: drillster/drone-volume-cache
rebuild: true
mount:
- ./node_modules
- ~/.cache
- ~/.npm
volumes:
- /tmp/cache:/cache
Desired behavior:
I ran my test pipeline on DroneCI and before was running version 2.x running smoothly.
I am trying to update the version to 3.0.2 and now Cypress complains that Binary is not being found, I have already tried some ways to solve with ENV variable and mount folder in cache step.
If anyone can help me, thank you.
Versions
Platform: linux (Debian - 8.10) Cypress: v3.0.2 DroneCI: v0.5
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:10 (5 by maintainers)
Top Results From Across the Web
Installation - drone docs
Binary Downloads. Download and install the raw binaries by platform: Platform, Download, Verify. Linux x64, tarball · checksum.
Read more >Drone CI/CD - container cannot find .NET SDKs - Stack Overflow
Everything looks fine. After drone finishes, the container does not start up,. Here's the error from the docker logs... docker logs 57 ...
Read more >How to set up Drone CI on Raspberry Pi (and why you shouldn't)
Some of these dependencies rely on binary files which may not be available for the arm processor used in a Raspberry Pi. As...
Read more >The Drone CI integration - Scala Center
The names of the subtasks are not important and must not be unique. ... Read Get latest Docker image if Drone keeps failing...
Read more >Error when compiling Anki in fedora (arm64) docker image on ...
The build takes place in drone ci using fedora 34 docker image. ... (INFO: Found 0 targets ) FAILED: Build did NOT complete...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Okay actually I know exactly what is happening.
What you’ve done or did (once) is that you cached the
node_modules
after Cypress installed.What this did was cache the CLI tool, but because now in
3.x.x
we install to the~/.cache
folder, when your CI provider goes to restore the cache, the binary is missing.Cypress is not being reinstalled because when you run
npm install
the Cypress npm module does not reinstall itself (cuz it’s already installed) which then prevents thepostinstall
hook from ever being called.I believe all you have to do is add a new command:
cypress install
and cypress will install itself if it doesn’t exist, or skip this step if it does.Can you run with
DEBUG=cypress:* npm install
orDEBUG=cypress:* cypress install
.I believe you can always issue
cypress install
and unless you pass the--force
flag it will not install if its already installed.We need more output logs from your CI provider. As it stands, there’s not enough to debug this. We have thousands of projects running on various CI providers but I’m not sure if we’ve seen Drone CI that often.