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

OSOE-464: Disabling node reuse during dotnet build and test #105

Merged
merged 7 commits into from
Nov 17, 2022

Conversation

Piedone
Copy link
Member

@Piedone Piedone commented Nov 16, 2022

@sarahelsaig sarahelsaig merged commit 536282a into dev Nov 17, 2022
@@ -69,6 +69,12 @@ dotnet build $SolutionOrProject @buildSwitches 2>&1 | ForEach-Object {
if ($noErrors) { Write-Output "::error file=$file,line=$line,col=$column::$message" }
}

# With node reuse, dotnet build spawns processes that while speed up build, they can cause dotnest test and other dotnet
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
# With node reuse, dotnet build spawns processes that while speed up build, they can cause dotnest test and other dotnet
# With node reuse, dotnet build spawns processes that while speed up build, they can cause dotnet test and other dotnet

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I always have to pay attention not to make this typo :D. I'll fix this in dev.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo? So it wasn't guerilla marketing?! 😱

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll sneak this change into the .NET SDK.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants