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

MSBuild Service - using MSBULDNOINPROCNODE env var #17308

Closed
rokonec opened this issue Apr 30, 2021 · 2 comments · Fixed by #17916
Closed

MSBuild Service - using MSBULDNOINPROCNODE env var #17308

rokonec opened this issue Apr 30, 2021 · 2 comments · Fixed by #17916
Assignees
Labels
build performance untriaged Request triage from a team member

Comments

@rokonec
Copy link
Contributor

rokonec commented Apr 30, 2021

Part of .NET 6.0 user story dotnet/msbuild#5873 as issue dotnet/msbuild#6392

Use existing MSBULDNOINPROCNODE escape hatch to improve consequent and incremental build scenarios.

Entry node will not compile any projects and will use reusable msbuild node(s) for it.
This way recompile or incremental compile might happen with hot caches resulting in considerably faster build time.

@dotnet-issue-labeler
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged Request triage from a team member label Apr 30, 2021
@rokonec rokonec self-assigned this Apr 30, 2021
@rokonec rokonec linked a pull request Jun 18, 2021 that will close this issue
@rokonec
Copy link
Contributor Author

rokonec commented Jun 18, 2021

Implemented and merged. We are still waiting for these changes to make it into Installer so we can see measurements and decide about this feature.

@rokonec rokonec closed this as completed Jun 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build performance untriaged Request triage from a team member
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant