Corrupted nuget package
Hi,
we use TC Nuget feed to distribute shared libraries in our company. One of the packages (let's call it Logging) recently stopped working. Some build agents are reporting the package missing. It's happening for all its versions we have.
After some digging we discovered that only agents where the package is no longer in their local cache are complaining. I checked the build artifacts in the project and all the "missing" versions are still there. So I went deeper, to the build server artifacts storage. There I discovered that just for this one package (all its versions there's a specific folder missing). Basically, every artifacts folder contains two files (.zip and .nupkg) and then a folder .teamcity. This folder then contains folders logs, nuget, properties and settings. But the problem is that for this package the nuget folder is completely missing.
Any idea why? I checked and no antivirus reports that it would delete or quarantine it.
Please sign in to leave a comment.
Hi Janacek,
Did versions which had worked in the past stop working as well? I get that hint from your message but I'm not entirely sure.
If that's the case, then it's likely that what has become corrupted is the nuget feed for that specific package. Reindexing it is likely to help here: https://confluence.jetbrains.com/display/TCD18/Common+Problems#CommonProblems-ProblemswithTeamCityNuGetFeed
Could you give that a try?
Hi Denis,
thank you for the tip. I have rebuilt the latest version of the missing package as a temporary solution before trying this. That helped. After clearing the cache, all the corrupted versions disappeared from the feed, which is nice but it really hasn't solved the problem. Once the packages disappear from the agents local caches (if that hasn't happened yet) we will get a lot of failing builds and will need to update the nuget package in all the failing projects.
My questions still remains unanswered then. Why did they got corrupted in the first place? Why did the nuget subfolder was removed?
Hi,
It's hard to say why the feed might have been corrupted. The reason I asked the question about previous versions of the package which had worked before was precisely to try to understand what might have produced the issue. TeamCity shouldn't remove the packages from the nuget feed (or remove the .nuget folders) unless the packages were requested for removal from the feed.
If you know when this happened, or see it happen again, you can check the teamcity-nuget.log files and the teamcity-server.log files, as there might be some information there. If you can find related information but would need help to process it, please consider sending those files to us via the "Submit a request" button on top of this page.