TeamCity (very nicely) generates a report tab named 'NuGet Packages' when you use any of the built-in NuGet runners to Install/Pack/Publish packages. Is it possible to populate this report when not using the built-in NuGet runners? For example: via NuGet.exe command line runner?
The built-in NuGet Installer runner requires a path to a Visual Studio solution file; however, NuGet.exe itself has no such requirement. We often install NuGet packages that have no correlation to Visual Studio projects, so we can't use the built-in NuGet Installer runner. We had to create our own Meta Runner that basically wraps NuGet.exe. Unfortunately, none of the packages installed with our custom Meta Runner appear on the NuGet Packages report tab.
As a workaround, we've been generating our own nuget.xml file and publishing this as an artifact (.teamcity/nuget/nuget.xml) which will correctly show packages installed via our custom Meta Runner on the report tab; however, this clobbers TeamCity's built-in mechanism and overwrites the internally-published nuget.xml. I was wondering if we could somehow make these "additive" rather than "exclusive."