* Move to new VMR control set
Now that msbuild is on 9.0 arcade, we can switch to the new control set. Generally:
- DotNetBuildFromSource -> DotNetBuildSourceOnly - Building a source-only build.
- DotnetBuildFromSourceFlavor == Product -> DotNetBuildOrchestrator == true - Building in the VMR, could be source-only or MS's build.
- ArcadeBuildFromSource -> DotNetBuildRepo == true -> Indicates an outer repo build.
* Rename sourcebuild.props -> dotnetbuild.props
* BuildManager instances acquire its own BuildTelemetry instance (#8444)
Fixes https://devdiv.visualstudio.com/DevDiv/_workitems/edit/1708215
Context
In VS there are multiple instances of BuildManager called asynchronously. For DTB and normal build and maybe other which I have not identified yet.
Changes Made
BuildManager instances acquire its own BuildTelemetry instance as oppose to sharing single BuildTelemetry instance in non thread safe manner.
Testing
Locally
# Conflicts:
# src/Build/BackEnd/Client/MSBuildClient.cs - resolved with minimal and safe approach
* Bumping version
* Turn off static graph restore. (#8498)
Our CI builds fails because of bug https://github.com/NuGet/Home/issues/12373.
It is fixed in https://github.com/NuGet/NuGet.Client/pull/5010.
We are waiting for it to flow to CI machines. Meanwhile this PR applies a workaround.
Note: This PR needs to be reverted once it happens.
---------
Co-authored-by: AR-May <67507805+AR-May@users.noreply.github.com>
Matt Mitchell
Viktor Hofer
Rainer Sigwald
Roman Konecny
Michael Simons
Livar Cunha
Livar