NuGet Publish
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 two 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
This page describes the NuGet Publish runner options:
Option | Description |
|---|---|
NuGet.exe | Select a NuGet version to use from the drop-down list (you need to have NuGet installed) , or specify a custom path to |
Packages | 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 |
Package Source | Specify the destination NuGet packages feed URL to push packages to, e.g. nuget.org. 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 If you work with an authenticated feed, configure the NuGet Feed Credentials build feature. Since TeamCity 2018.2, TeamCity will use the credentials provider to automatically authenticate requests to build-in NuGet feeds or feeds specified in the NuGet feed credentials build features. Note that API v1/v2 feeds require NuGet 2.0+; NuGet 3.5+ is recommended. API v3 feeds require NuGet 4.8+ or NuGet 4.9+ on Mono. 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 |
or manually specify the URL from the