feat(cypress): Always run cypress CI in parallel #41039
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
The server always exceeds the free Cypress.io time so there is no benefit using it unless we go for the enterprise plan.
So this simply uses
cypress-split
to split the specs and run them in parallel CI workers (only e2e tests).Prevent this:
By simply using some split logic in the CI runs without external dependency on Cypress.io
Results
Seems to work fine, of cause this has no "intelligent" load balancing as using the Cypress cloud, but it still is better than always running out of time and stuck with no parallelization at all.
Checklist