Skip to content

Conversation

@akoeplinger
Copy link
Contributor

In the pipeline dotnet restore was accidentally not using the nuget.config in the repo since we ran dotnet from the checkout root. Instead we can set workspaceRoot: true on the crank checkout step to make it the default working directory.

This fixes network isolation violations in the pipelines.

/cc @LoopedBard3 @sebastienros

In the pipeline dotnet restore was accidentally not using the nuget.config in the repo since we ran dotnet from the checkout root.
Instead we can set `workspaceRoot: true` on the crank checkout step to make it the default working directory.

This fixes network isolation violations in the pipelines.
@akoeplinger
Copy link
Contributor Author

Copy link
Contributor

@LoopedBard3 LoopedBard3 left a comment

Choose a reason for hiding this comment

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

Great catch! This looks good to me.

@akoeplinger
Copy link
Contributor Author

I don't have permissions to merge :)

@sebastienros sebastienros merged commit 5643540 into aspnet:main Dec 5, 2025
2 checks passed
@sebastienros
Copy link
Member

sebastienros commented Dec 5, 2025

@akoeplinger you can join this team if you want, also works for aspnet

@akoeplinger akoeplinger deleted the fix-nuget-restore branch December 5, 2025 15:18
@akoeplinger
Copy link
Contributor Author

thanks. the OSS portal is down right now, will do once it's back up.

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