Teamcity fails at nuget restore step when package exists
We a are occasionally having issues in TeamCity with the nuget restore step, It would fail and say error
NU1102: Unable to find package {PackageName} with version (>= 0.0.162) C:\TeamCity\buildAgent\work\74e7fed33e9915c9\
When in fact the version 0.0.162 is in our private nuget server.
We are using
.NET Command Line Tools (2.1.105)
Product Information:
Version: 2.1.105
Commit SHA-1 hash: 141cc8d976
Runtime Environment:
OS Name: Windows
OS Version: 10.0.14393
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\2.1.105\
Microsoft .NET Core Shared Framework Host
Version : 2.0.7
Build : 2d61d0b043915bc948ebf98836fefe9ba942be11
TeamCity version
2017.2.3 (build 51047)
Please let me know if you can think of any suggestions
Please sign in to leave a comment.
Hi,
For us to be able to help trace the issue, we would need to know not just what you are using, but how you are using it. The build log from the start of the build step (including the type of runner) until the error message would be the minimum we would need to see before being able to provide any useful help.
Hi Good afternoon and thank you for your response.
I came to Common denominator, When the packages fail. And here are the details
When i am doing just a package update (new version for our internal nuget server) and Commit the code the build will fail. If we do a package update and also a very minor code change manly a code deletion the build will still fail. unless we would a new addition to code it will will go succeed is this by design?