Icon

You are viewing the documentation of TeamCity 9.x, which is not the most recently released version of TeamCity.
View this page in TeamCity 10.x and 2017.1 documentation or refer to the listing to choose the documentation corresponding to your TeamCity version.

 
Skip to end of metadata
Go to start of metadata

The NuGet Dependency Trigger allows starting a new build if a NuGet packages update is detected in the NuGet repository.

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

  1. 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;
  2. Specify the NuGet package source, if it is different from nuget.org;
  3. Specify the credentials to access NuGet feed if required
  4. Enter the package Id to check for updates.
  5. 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 check box. Note that this is only supported for NuGet version 1.8 or newer.



See also:

Administrator's Guide: NuGet

  • No labels