CI: Further Parallelize Execution Of Jest Tests #4324
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
adrians5j
changed the title
adrians5j
changed the title
adrians5j
changed the title
brunozoric
approved these changes
Oct 15, 2024
brunozoric
approved these changes
Oct 15, 2024
brunozoric
pushed a commit
that referenced
this pull request
Nov 5, 2024
brunozoric
pushed a commit
that referenced
this pull request
Nov 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Changes
With this PR, we are further parallelizing execution of Jest tests, using Jest's sharding feature. Packages
api-headless-cmsandapi-page-builderwill now be executed across 6 parallel processes.These changes are applied to PR (
pullRequests.yml) and push workflows (pushDev.yml,pushNext.yml).Note
I'm not yet sure if 6 is the optimal number when it comes to the number of shards. What I saw in tests is that, with this number set to 10, ES-related tests would fail more often. Probably because ES would get overloaded during the execution of tests. We'll be monitoring logs a bit in the following days and see how things behave.
Results
With the above mentioned changes, the PR workflow duration was reduced from 30-40min to 15min-25min.
Additional Changes
I've removed Publish to Verdaccio and
create-webiny-projectjobs from the PR workflow, because:How Has This Been Tested?
CI.
Documentation
N/A