TeamCity 2020.1 Help

NuGet Publish

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

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 list (you need to have NuGet installed ), or specify a custom path to NuGet.exe.


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

API key

Specify the API key to access a NuGet packages feed.

To publish to the TeamCity NuGet server, specify the %teamcity.nuget.feed.api.key% parameter.

Package Source

Specify the destination NuGet packages feed URL to push packages to, for example, Leave blank to let NuGet decide what package repository to use. If you are using a TeamCity NuGet feed, select it using the 'magic wand' icon magic-wand.png or manually specify the URL from the NuGet Feed section of the Project Settings.

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 ?replace=true parameter, for example, http://<Teamcity URL>/httpAuth/app/nuget/feed/NuGet/default/v2?replace=true.

Command line parameters

Enter additional parameters to use when calling the nuget push command.

Last modified: 13 May 2020