Prevent TeamCity from saving NuGet Packages Artifacts Follow
Referring to this old forum discussion (https://teamcity-support.jetbrains.com/hc/en-us/community/posts/115000440904-Prevent-Teamcity-from-saving-NuGet-Package-Artifacts), TeamCity will automatically add a NuGet package to the builds artifacts when the NuGet Publish task is used.
Does this happen regardless of where the NuGet Feed is stored? For example, an external package server?
How can I prevent just the NuGet Packages from being saved as an artifact. I need to do this globally.
Please sign in to leave a comment.
The reason your NuGet packages are published as build artifacts whenever you publish them to a built-in feed is that the built-in feed uses TeamCity artifact storage to store packages in. If you choose to publish your packages to an external feed, they will not have to be published as build artifacts.
All of our NuGet packages are pushed to an external feed using the NuGet Publish runner task.
We have explicitly disabled the internal NuGet feed.
Any ideas why they are being stored as artifacts?
You should check the build configuration's General Settings > Artifact paths. Whatever files are matched by the specified artifact paths will get published.
Also, if you use the NuGet Pack step, see whether Publish created packages to build artifacts is ticked.