You are viewing the documentation of TeamCity 9.x, which is not the most recently released version of TeamCity.
View this page in TeamCity 2018.x documentation or refer to the listing to choose the documentation corresponding to your TeamCity version.

Skip to end of metadata
Go to start of metadata

The NuGet Publish build runner is intended to publish (push) your NuGet packages to a given feed (custom or default).


If you're using TeamCity as a NuGet server, you don't need to add this build step. However, the output of the NuGet Pack build step should be a build artifact: specify the path to it in the General Settings of your build configuration.


NuGet Publish is only supported on build agents running Windows OS.

This page describes the NuGet Publish runner options:




Select a NuGet version to use from the drop-down list (if you have installed NuGet beforehand), or specify a custom path to NuGet.exe.


An appropriate version of .NET Framework installed on the agent machine is required depending on the NuGet.exe version used: NuGet 2.8.6+ requires .NET 4.5+, NuGet 2.5.x requires .NET 4.0.


Specify a newline-separated list of NuGet package files (.nupkg) to publish to the NuGet feed. List packages individually or use wildcards.

Only upload packages but do not publish them to feed

Select the checkbox if you want to upload your package to the TeamCity server but keep it invisible in the feed. Works for NuGet versions 1.5 and older.

API key

Provide your API key.

Package Source

Specify the destination NuGet packages feed URL to push packages to, by default it is nuget.org. If you have your own NuGet server, specify its address here.

See also:

Administrator's Guide: NuGet Installer | NuGet Pack

  • No labels