Fix parallel builds #2563
Closed
Fix parallel builds #2563
Conversation
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
timcassell
force-pushed
the
fix-parallel-builds
branch
2 times, most recently
from
286de66 to
3285f50
Compare
MonoPublisher inherits from DotNetCliBuilderBase. Don't repeat sequential builds.
timcassell
force-pushed
the
fix-parallel-builds
branch
from
3285f50 to
2b4c775
Compare
Collaborator
Author
|
Closing in favor of #2676. |
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.
Fixes #2425
Builds using dotnet sdk 8 or newer use
ArtifactsPathto enable safe parallel builds. Builds using older dotnet sdks and wasm and monoaotllvm build sequentially.It would be nice to enable parallel builds also for wasm and monoaotllvm, but I can't test them on my machine, so I'm not sure why it doesn't work with those toolchains. cc @LoopedBard3 @caaavik-msft