Unable to render embedded object: File (TeamCity48.png) not found.

TeamCity 10.x and 2017.x Documentation


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


Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: related to https://youtrack.jetbrains.com/issue/TW-20855


  • NuGet feed based on the builds' published artifacts
  • A set of NuGet runners to be used in builds on Windows OS:
    • the NuGet Installer build runner, which installs and updates NuGet packages
    • the NuGet Pack build runner, which builds NuGet packages
    • the NuGet Publish build runner, which publishes packages to a feed of your choice.
  • The NuGet Dependency Trigger Trigger, which allows triggering builds on NuGet feed updates.
  • NuGet build runners are only supported on build agents running Windows OS.
  • NuGet build runners runners require an appropriate version on .NET Framework installed on the agent machine depending on the NuGet.exe version used: NuGet 2.8.6+ requires .NET 4.5+, earlier NuGet versions require .NET 4.0.
  • To use packages from an authenticated feed, see the NuGet Feed Credentials build feature.




  1. Go to the Administration | Tools tab.
  2. Click Install tool and select NuGet.exe.
  3. Select whether you want to download (default) NuGet from the public feed or upload your own NuGet package containing NuGet.exe.

    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. 

  4. 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:

  • You

    don'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.