Implement build parallelism and default to parallel builds#152
Merged
Conversation
Allow setting job count with `MAX_JOBS` environment variable
`MAX_JOBS` can still be used as an override in the (unlikely) case that something is wrong.
Contributor
Author
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Closes gh-28
Closes gh-105
The first commit takes over the change in PR gh-105 (keeping authorship), because that change is aimed at the old
masterbranch rather than atmain.The second commit makes parallel builds the default, which should be safe enough and is what all modern build systems do. It really speeds up CI jobs, which is a nice benefit. For example:
From the last wheel build run on
main:From running those same jobs on my fork (CI log: