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

nuget-client repo uses the VMR package cache instead of repo local #4293

Closed
ViktorHofer opened this issue Apr 4, 2024 · 3 comments
Closed
Labels
area-additional-repos Adding additional contributing repos untriaged

Comments

@ViktorHofer
Copy link
Member

image

All other repos in the VMR use a separate repo specific package cache.

@ViktorHofer
Copy link
Member Author

cc @mthalman as this could result in build order issues with the now enabled parallel builds

@corngood
Copy link

@ViktorHofer I inadvertently 'fixed' this by adding <ItemGroup><EnvironmentVariables Include="NUGET_PACKAGES=$(ProjectDirectory)artifacts/sb/package-cache/"... to repo-projects/nuget-client.proj, while I was trying to get packages in consistent locations for dependency gathering (#4333).

this could result in build order issues with the now enabled parallel builds

I think that's exactly what I discovered and attempted to fix here:

NuGet/NuGet.Client#5756

I don't think it's related to parallel builds, but I think these missing packages were restored by previous repos when using a shared packages dir.

@ViktorHofer
Copy link
Member Author

I think this already got fixed by NuGet/NuGet.Client#5749, cc @mmitche

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-additional-repos Adding additional contributing repos untriaged
Projects
Archived in project
Development

No branches or pull requests

2 participants