[release/9.0.1xx-preview7] Re-Bootstrap Source Build to .NET 9.0.100-preview.7.24373.1 #42371
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.
Description
Backport of #42343 to release/9.0.1xx-preview7
/cc @ellahathaway @dotnet-sb-bot
This is required to fix intermittent failures in the source-build product. The failures were originally reported in msbuild as dotnet/msbuild#10342. These failures were also reported in source-build in dotnet/source-build#4521 and dotnet/source-build#4515.
A re-bootstrap refers to the process of updating the initial bootstrapped toolset used to build a project. In the context of the .NET SDK, it involves acquiring an updated bootstrapping .NET SDK.
Re-bootstrapping is necessary when new functionality is added to the bootstrap toolset that the project needs to depend on. In this particular instance, source-build was experiencing the msbuild failures because the msbuild failures were in the bootstrapped toolset. In order to resolve the failures, we need to upgrade the toolset (rebootstrap) used to build source-build in order to consume the fix.
This affects source-build only.
Customer Impact
This is a build reliability issue that will impact distro maintainers.
Regression?
This issue first appeared in main (preview7), and we branched for preview7 before the fix went into main.
If this is not taken, a regression will be introduced into preview7.
Risk
Low