Parallelize CircleCI jobs using workflows #15704
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
Updates the CircleCI config to use the workflows features to run jobs in parallel, instead of the `parallelism` option. This change alone doesn't improve the overall build time much, since almost all of the total time is spent running the Rollup script, which runs entirely sequentially. But it does improve reporting, and should make it easier to add additional parallel jobs in the future.
acdlite
force-pushed
the
use-circleci-workflows
branch
12 times, most recently
from
4e39d37 to
65754f4
Compare
acdlite
changed the title
acdlite
force-pushed
the
use-circleci-workflows
branch
from
65754f4 to
fecd448
Compare
|
ooooo very nice |
|
Slick! |
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.
Updates the CircleCI config to use the workflows feature to run jobs in parallel, instead of the
parallelismoption. This change alone doesn't improve the overall build time much, since almost all of the total time is spent running the Rollup script, which runs entirely sequentially. But it does improve reporting, and should make it easier to add additional parallel jobs in the future.(My original motivation for this PR was because I want to use a workflow trigger to run a chron job for the fuzz tester.)
PRs report more granular information about the CI status:
The Workflows view includes a nice flowchart. Note how the Rollup script takes the bulk of the time, as you would expect. (Parallelizing that step would be an easy win.)