2

I've set up TeamCity (9.1.6) to work as a NuGet server. I have a project that I added a NuGet Pack build step. The artifacts of that build configuration are *.nupkg files.

However, when I view either the authenticated or the guest NuGet feed, the package list is empty.

I've reset the buildMetadata cache and even restarted the build server.

What am I missing?

Edit: here's what the artifacts looks like for my project:

enter image description here

kenstone
  • 526
  • 7
  • 14
  • I have the same problem. NO matter what I do, the feed is empty. All *.nuget files are published, the server is configured, I check both the auth and non-auth feed and they are empty. Nothing. – David Dombrowsky Nov 17 '16 at 21:40

2 Answers2

3

If the .nupkg isn't showing as an artifact then it won't be in the feed. Without knowing the output directory settings, I can't tell you the correct value for the build artifact path. However, the simplest option is to ensure the checkbox is ticked that forces packages to be published as build artifacts.

enter image description here

Hope this helps

Matt
  • 3,684
  • 1
  • 17
  • 19
  • The .nukpg files *are* in my build artifacts (my question briefly noted this). I've updated my question with a screenshot of the artifacts for the project. Thanks for your help so far. – kenstone Jun 17 '16 at 14:14
  • How are you accessing the NuGet feed? – Matt Jun 17 '16 at 14:29
  • Viewing raw feed in a browser. Packages collection is empty. – kenstone Jun 17 '16 at 14:33
  • 2
    Ah. It does this :( Add the feed as a package source to something like Visual Studio and you'll see your packages. – Matt Jun 17 '16 at 15:01
  • 1
    Wow. That is just weird. I swear I had tried it in Visual Studio earlier and it showed nothing. But I just redid everything and there it is. Thanks for your help. – kenstone Jun 17 '16 at 15:56
  • 1
    Ah. I discovered that it wasn't showing up in studio because the NuGet packages were targeting a higher version of the framework than the project I was adding them to. Once I updated the project to match the framework version, they showed up as expected. – kenstone Jun 17 '16 at 16:06
  • All packages have that "publish" box checked. Target versions of .NET match. I'm viewing it in Visual Studio. Nothing. EDIT -> Turns out that not all the binaries were configured to use the same target version. If only one in the solution is incorrect, the packages won't show up. That was the problem. – David Dombrowsky Nov 17 '16 at 21:46
0

I had this same exact issue, and it eventually worked.

My issue was I was running Personal Builds not Full Builds. Even though it would still make the package as an artifact, it wouldn't publish to the newsfeed.

[Step 15/15] Packages from personal builds are not published to ******* NuGet Feed

It even said as much in the Build Log (as shown above)

Dan
  • 429
  • 3
  • 9