- NuGet feed based on the builds' published artifacts
- A set of NuGet runners to be used in builds on Windows OS:
- The NuGet Dependency Trigger Trigger, which allows triggering builds on NuGet feed updates.
- To install packages from a public feed, add the NuGet Installer build step.
- To create a package and publish it to a public feed, add the NuGet Pack and NuGet Publish build steps.
- To trigger a new build when a NuGet package is updated, use NuGet Dependency Trigger.To create a package and publish it to the internal TeamCity NuGet Server, enable TeamCity as a NuGet Server (see the section below), use the NuGet Pack build step and properly configure artifact paths.and NuGet Publish build steps.
- To trigger a new build when a NuGet package is updated, use NuGet Dependency Trigger.
- Go to the Administration | Tools tab.
- Click Install tool and select NuGet.exe.
Select whether you want to download (default) NuGet from the public feed or upload your own NuGet package containing
a) If the Download radio button is chosen, select the NuGet version to install on all build agents.
It is recommended to use release versions of NuGet.
b) If the Upload radio button is selected, choose your own NuGet package.
Specify whether this NuGet version will be default using the related check-box.
- Click Add to install the selected NuGet version.
When the NuGet Server is enabled, all NuGet packages published as TeamCity build artifacts will packages will be indexed and will appear in NuGet feed. The feed will include the packages from the build configurations where the currently authenticated user has permission to view build artifacts ("View project" permission).
Since TeamCity 2017.1, TeamCity supports publishing of NuGet packages to TeamCity from NuGet Publish build runner.
When you have TeamCity NuGet server enabled:
Youdon't need to use NuGet Publish build step (unless you want to publish packages on some public feed), only specify NuGet packages as TeamCity build artifacts.
can publish packages to the feed either 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) or via the NuGet Publish build step (since TeamCity 2017.1)
You can add TeamCity NuGet server to your repositories in Visual Studio to avoid having to type in long URLs each time you want to read from a specific package repository (add NuGet repository and specify the public URL provided by TeamCity when enabling NuGet server).
The packages available in the feed are bound to the builds' artifacts: they are removed from the feed when the artifacts of the build which produced them are cleaned up.
Since TeamCity 9.1.4, you You do not need to specify credentials for the internal NuGet feed access; if NuGet Feed Credentials are specified, they are ignored.