Remove runtime Helix MSBuild parallelism override - #131831
Open
jkoritzinsky with Copilot wants to merge 3 commits into
Open
Remove runtime Helix MSBuild parallelism override#131831jkoritzinsky with Copilot wants to merge 3 commits into
jkoritzinsky with Copilot wants to merge 3 commits into
Conversation
|
Azure Pipelines: 16 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
Contributor
|
Tagging subscribers to this area: @dotnet/area-infrastructure-libraries |
Co-authored-by: jkoritzinsky <1571408+jkoritzinsky@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Remove msbuild parallelism after Helix Job Monitor enablement
Remove runtime Helix MSBuild parallelism override
Aug 4, 2026
Co-authored-by: jkoritzinsky <1571408+jkoritzinsky@users.noreply.github.com>
jkoritzinsky
approved these changes
Aug 4, 2026
jkoritzinsky
marked this pull request as ready for review
August 4, 2026 21:54
|
Azure Pipelines: Successfully started running 5 pipeline(s). 11 pipeline(s) were filtered out due to trigger conditions. There may be pipelines that require an authorized user to comment /azp run to run. |
This was referenced Aug 5, 2026
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
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.
main PR N/A
Description
Runtime test Helix submission no longer needs to force high MSBuild parallelism now that the Helix Job Monitor is enabled. This PR removes the runtime send-to-Helix
/maxcpucount:55override and its stale rationale, allowing the shared default/maxcpucountbehavior to apply.msbuildParallelism: '/maxcpucount:55'override fromrun-test-job.yml.Customer Impact
No product runtime impact. This simplifies CI infrastructure behavior for runtime test Helix submissions.
Regression
No. This intentionally changes CI submission parallelism after Helix Job Monitor enablement.
Testing
Not included in this description.
Risk
Low. The change is limited to runtime test pipeline YAML and falls back to the existing shared send-to-Helix default.
Package authoring no longer needed in .NET 9
IMPORTANT: Starting with .NET 9, you no longer need to edit a NuGet package's csproj to enable building and bump the version.
Keep in mind that we still need package authoring in .NET 8 and older versions.