The NuGet Publish build runner is intended to publish (
push) your NuGet packages to a given feed (custom or default).
When using TeamCity as a NuGet server, there are three ways to publish packages to the feed:
as build artifacts of the NuGet Pack build step using the Publish created packages to build artifacts checkbox - in this case you do not need the NuGet Publish build step
via the NuGet Publish build step
##teamcity[publishNuGetPackage]service message, which ensures the packages are published in all configured NuGet feeds at the end of the current build step and are available in the following build steps
Supported Operating Systems:
NuGet build runners are supported on build agents running Windows OS by default. Linux and macOS are supported when Mono is installed on the agent (only NuGet 3.3+ on Mono 4.4.2+ is supported).
This page describes the NuGet Publish runner options:
Select a NuGet version to use from the drop-down menu (you need to have NuGet installed ), or specify a custom path to
Specify a newline-separated list of NuGet package files (
Specify the API key to access a NuGet packages feed.
To publish to the TeamCity NuGet server, specify the
Specify the destination NuGet packages feed URL to push packages to, for example,
If you work with an authenticated feed, configure the NuGet Feed Credentials build feature.
TeamCity allows you to authenticate using private NuGet feeds. Read more in NuGet.
Replacing existing package version in TeamCity internal feed
When publishing a package with the same version that already exists in a TeamCity internal NuGet feed, the package will be rejected. To force the TeamCity server to replace the existing NuGet package with a new version, append your feed URL obtainable from the Project Settings page with the
Command line parameters
Enter additional parameters to use when calling the