Nuget packages included in artifacts automatically

1
votes

We have a TeamCity build server and for a time were had the internal Nuget server enabled. We'd generate Nuget packages, which it'd automatically publish to the nuget feed.

We've since moved to another Nuget server and disabled the TC internal Nuget server; additionally we started building Nuget packages using OctoPack in some configurations which never built them before. The problem is that these Nuget packages seem to automatically be added to the build configuration's Artifacts. This is a waste, since the same packages are being published to the external (to TeamCity) Nuget server.

Is there a setting which automatically will find and include Nuget packages in TeamCity's artifacts, or is it just doing this on its own? I cant even explicitly exclude the packages in the configuration's artifacts setting, they get included regardless.

TeamCity is version 2018.1.2.

1
nugetteamcityoctopus-deploy
If your Artifacts Path is set correctly. Can you try to reset relevant cache elements or create an entirely new Build Configuration and see if it the issue is reproducible. Warning: If you are trying to reset cache do it at your own risk since can have adverse effects. – Ankit Vijay

1 Answers

0
votes

New packages in built-in TeamCity NuGet feeds could be added via the followings ways.

So to avoid publishing produced nuget packages as a build artifacts inspect:

  • Artifact paths settings in your build configuration
  • NuGet Pack build steps settings: uncheck "Publish created packages to build artifacts" option
  • NuGet Publish build steps settings: don't specify TeamCity built-in NuGet feed URLs in "Package source" field.