NuGet Dependency Trigger
The NuGet dependency trigger allows starting a new build if a NuGet packages update is detected in the NuGet repository.
note
Currently, the NuGet dependency trigger supports only API versions 1 and 2 due to specifics of the Nuget.CommandLine tool.
Requirements and limitations
For a TeamCity server running on Windows, .NET 4.0 is required.
For a TeamCity server running on Linux, the NuGet dependency trigger will reportedly work with the following limitations:
filtering by Package Version Spec is not supported
only HTTP package sources are supported
NuGet feed version 1.0 is used, so case-sensitivity issues might occur
the current trigger implementation on Linux might increase the server load
authentication issues might occur
Configuring NuGet Dependency Trigger
Select the NuGet version to use from the NuGet.exe drop-down list (if you have installed NuGet beforehand), or specify a custom path to
NuGet.exe;Specify the NuGet package source, if it is different from
nuget.org;Specify the credentials to access NuGet feed if required
Enter the package Id to check for updates.
Optionally, you can specify package version range to check for. If not specified, TeamCity will check for latest version.
You can also opt to trigger build if pre-release package version is detected by selecting corresponding checkbox. Note that this is only supported for NuGet version 1.8 or newer.