I have upgraded to TeamCity 2017.1.1 yesterday from v10, and since then, all new artifacts produced by build configurations no longer get published to the internal nuget feed service.
I have retried clear the buildsMetadata cache, and also tried running the build configurations multiple times to make it's not some sort of caching issue etc.
The build configurations do not use Nuget build steps of any sort (we have our own custom scripts that run as powershell build steps that creates the packages automatically), and relies on TeamCity to automatically publish artifact outputs directly to the internal nuget feed.
The old build artifacts seems to be present in the internal nuget feed, but they are all from prior to the upgrade.
No actual configurations had changed since the upgrade to the build configurations as well.
I am currently working around this problem by adding an extra Nuget Publish step for my build configurations to force publish the artifact outputs into the internal nuget feed.
Is this a known issue?