Team City Nuget Feed not working (or very slow to update) after update to 2019.1.4 (build 66526)
Hi,
Since updating to 2019.1.4 (build 66526) this morning, our nuget feeds don't seem to be getting updated, its telling us the version of the file we want can't be found (it CAN be found using the package manager in VStudio, which is how we reference it), So it seems like the feed is taking a while to update the packages
This has only become a problem this morning after updating to the latest version
Please sign in to leave a comment.
Hi Tony,
thanks for your report. We have seen a second instance of this issue recently and we are investigating, but haven't managed to reproduce the problem just yet. It would be helpful if you could provide us with:
-A screenshot of the nuget feed settings
-A full build log of a non-indexed build
-The teamcity-nuget.log from the server.
Please use the "Submit a request" button above to send those to us.
Hi Tony,
One more question. Could you please tell me if I get you right:
1. You have one build configuration that prepares and pushes the NuGet package to an internal TeamCity NuGet Feed.
2. After that, you see this package in Visual Studio and use it in your project.
3. Another build configuration that builds that project fails to restore the package from the feed.
If it is all right, could you please also attach a build log for the second build configuration?
Hi, sorry for not being more concise, Nadia is correct in my use case and issues
I have provided the files requested on the following request:
Request #2312671
please let me know if there is anything further you require
Kind Regards
Tony
We have also encountered what looks to be this issue since upgrading to 2019.1.4.
Our continuous deployment pipeline involves TeamCity building and publishing packages to nuget feed and triggering an OctopusDeploy deployment to our QAS system. Since upgrading TeamCity we have had confusing instances of errors in both our QAS and PRD system we have traced back to the Octopus deployements intermittently finding only the previous version in the TeamCity nuget feed. Ideally this would have triggered an error or warning during the Octopus deployment but the root cause appears to relate to this TeamCity nuget feed update issue.
We have worked around the issue in our case by pushing artifacts to Octopus Deploy internal feed with a build step in between packaging and triggering deployment.
Prior to implementing this workaround I noted the following:
Adding a delay between build/package and deployment had no effect - I tried implementing both on TeamCity and Octopus side.
No matter how long I waited - the artifacts that were missing from the feed only appeared in the feed after the entire build configuration had completed. This was despite absolutely no difference between how these artifacts were built or packaged compared to those that were appearing immediately. The clear pattern was it was the last package published that was missing - or in some cases the last n packages.
Looking closer at timestamps in logs - it appears any package that completed publishing prior to the build/package step completeing/exiting was available immediately - while any that completed publishing subsequently were not available/indexed until the end of the entire teamcity build.
Hopefully this information can be of some use in tracking down the problem.
It is entirely possible this was an issue prior to version 2019.1.4 but has just become more frequent and noticable due to some other factor leading to more frquent 'post-step' completion of artifact publishing.
Hi Sascha,
Thank you for the detailed description of the problem. We have the following issue in our YouTrack. We think that we found and fixed the problem that can lead to the behavior that you described. Could you please try to install the plugin version from the issue on your server and tell us if it solves the problem?
We're having a seemingly similar situation to this. We're on TeamCity Enterprise 2021.2 (build 99542), have a build process set up to create a package, and an explicit pack step to push it to the local feed.
Subsequent builds that depend on that package are unable to find said package, though the package can somehow be found through rider.
One other oddity, when going through the feed json (...guestAuth/app/nuget/feed/_Root/RootNuGetFeed/v3/query), the package version is *not* showing up, but is still somehow browsable from rider. the feed URL being used from rider is in the form: