You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, please help to understand why wrong "packagesPath" appears after nuget restore on CI.
Context:
we use Windows Server 2022 which runs two TeamCity build agents BA03-A and BA03-B. Each build agent runs as a different user, and uses own nuget folders:
From time to time (we don't have stable reproduction) after dotnet restore we get wrong packages file paths under projects obj folder - in the projects.nuget.cache files and .nuget.dgspec.json files. The BA03-B build agent gets paths to the another user nuget packages directory (BA03-A). We do clean checkout, so this is not remnants from previous builds.
This is build from user BA03-B, but paths points to BA03-A user directory:
At the later stage, this discrepancy makes dotnet publish fail.
Please help to understand what happens and how dotnet restore can get end up with paths from a different user?
PS. This does not happen when we use globalPackagesFolder setting in NuGet.config. Only when we switch to the default setup with the packages folder under the user's directory.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello, please help to understand why wrong "packagesPath" appears after nuget restore on CI.
Context:
we use Windows Server 2022 which runs two TeamCity build agents BA03-A and BA03-B. Each build agent runs as a different user, and uses own nuget folders:
Problem:
From time to time (we don't have stable reproduction) after
dotnet restore
we get wrong packages file paths under projectsobj
folder - in theprojects.nuget.cache
files and.nuget.dgspec.json
files. The BA03-B build agent gets paths to the another user nuget packages directory (BA03-A). We do clean checkout, so this is not remnants from previous builds.This is build from user BA03-B, but paths points to BA03-A user directory:
At the later stage, this discrepancy makes
dotnet publish
fail.Please help to understand what happens and how
dotnet restore
can get end up with paths from a different user?PS. This does not happen when we use
globalPackagesFolder
setting in NuGet.config. Only when we switch to the default setup with the packages folder under the user's directory.We use SDK version 6.0.414
Beta Was this translation helpful? Give feedback.
All reactions