Add options to prune command
See original GitHub issueWhat would you like?
We’d like some options added to the prune
command that would allow some flexibility in regards to which versions it deletes. We would like to add this to our CI pipeline but would run into the issue where if two branches had different versions of Cypress running (e.g. one on 6.2.0 and one just updated to 6.2.1) that they would each delete the other install.
I was thinking something along the lines of one option that would allow you to disable deleting higher versions (e.g. an old branch with Cypress 3.6.0 runs and doesn’t kill our current version of 6.2.1) and an option to keep the last version or two of Cypress installed (e.g. one branch updates from 6.2.0 to 6.2.1 and it doesn’t delete 6.2.0 as it is just one version behind).
Why is this needed?
Allow running command as part of CI pipeline, see above.
I’d be willing to have a go at the PR if this feature sounds reasonable.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:5 (4 by maintainers)
We’ll be working automatic cache pruning as part of cypress provided browser binaries see issue #19278
It would be nice to have this feature so that there isn’t churn when moving between Cypress versions…