In CI, cypress install should clear old cached versions
See original GitHub issueProposal: Prevents large buildup of ~/.cache
with obsolete versions. Should only happen in CI because locally users could have multiple versions installed on the system in other projects.
complications:
- different cypress versions across branches, can’t clear out other versions…
Issue Analytics
- State:
- Created 5 years ago
- Reactions:4
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Troubleshooting | Cypress Documentation
If you're having an issue during installation of Cypress, try removing the contents of the Cypress cache. This will clear out all installed...
Read more >Clean Cypress cache in GitHub CI - Stack Overflow
You can use the command to delete all previously installed versions of cypress. cypress cache prune.
Read more >Caching Dependencies - CircleCI
This document is a guide to caching dependencies in CircleCI pipelines. ... With dependencies restored from a cache, commands like yarn install need...
Read more >Specify NPM dependencies for Cypress tests - BrowserStack
Caching dependencies is a default behavior for browserstack-cypress-cli v1.11.0 and higher. Due to this behavior, all your private packages (if any) would also ......
Read more >Caching node modules and Cypress installation in an azure ...
After a few trial and error, I finally got the build to run Cypress tests and cache the binaries. Keep in mind that...
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
This is now possible with
cypress cache prune
. Closing as resolved.If you’re experiencing a bug similar to this in Cypress, please open a new issue with a fully reproducible example that we can run. There may be a specific edge case with the issue that we need more detail to fix.
Yep, I could definitely see that being useful too!
Given that
cypress version
already knows the version (it looks like throughutil.pkgVersion()
), creating a loop to iterate through all other versions in the cache directory and delete them doesn’t seem too farfetched.My vote is to add a command along the lines of
cypress cache clear stale
that clears all versions except for the one returned bycypress --version
.