(chore) Limit workflow task parallelization #688
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
This PR limits the number of tasks that run in parallel in our CI workflow. This is so as to reduce the likelihood of the CI workflow execution running out of memory. It does so by separating the `lint` and `typescript` jobs into their own pipeline that is separate from the `build` job.
|
Why not use the |
Sure. I still reckon it's sensible to separate the formatting and type checking jobs from the build step. It'd be easier to determine what resources to allocate to the two jobs when separate. The build job concurrency likely needs tweaking downwards to mitigate resource use, whereas the formatting jobs could go full turbo. |
brandones
approved these changes
May 9, 2022
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.
Requirements
Summary
This PR limits the number of tasks that run in parallel in our CI workflow. This is to reduce the likelihood of the CI workflow execution running out of memory.
It does so by factoring out the
lintandtypescriptjobs into their own pipeline, separate from thebuildpipeline.