Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release/7.0.1xx] Disable msbuild server by default #28369

Conversation

AR-May
Copy link
Member

@AR-May AR-May commented Oct 6, 2022

Summary

This PR makes MSBuild server an opt-in feature for 7.0 SDK, instead of opt-out. Given the recent failures in the dotnet/runtime repo when using this feature (dotnet/runtime#75391), we would like to have more time to fix the bugs and dogfood before it becomes an opt-out feature.

Customer Impact

Revert to 6.0-and-previous behavior, avoiding new instability (but not getting new perf improvements).

  • This fix would remove instability of dotnet build introduced by the opt-out MSBuild Server feature.
  • Customers would still have an option to use the feature.

Regression?

Yes--server failed in some new cases.

Testing

Unit tests.

Risk

Low risk.

Description of the fix

We ignore DOTNET_CLI_DO_NOT_USE_MSBUILD_SERVER opt-out env. variable and use an opt-in DOTNET_CLI_USE_MSBUILD_SERVER env variable instead to control the MSBuild Server feature in SDK CLI.

@AR-May AR-May changed the title [release/7.0.1xx] Make msbuild server opt in 7.0.1xx [release/7.0.1xx] Change default for msbuild server. Oct 6, 2022
@rainersigwald rainersigwald changed the title [release/7.0.1xx] Change default for msbuild server. [release/7.0.1xx] Disable msbuild server by default Oct 6, 2022
@rbhanda rbhanda added this to the 7.0.0 milestone Oct 6, 2022
@build-analysis build-analysis bot mentioned this pull request Oct 6, 2022
2 tasks
@marcpopMSFT marcpopMSFT merged commit dc92a6e into dotnet:release/7.0.1xx Oct 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants