This new version seems to break the publishing to the teamcity nuget server. It successfully publishes the database package to the server, but then gets an exception and fails the build. If you go to the deployment manager and search for the new package it was published. This was all working fine on the previous release and only broke after we upgraded.

Also I had to delete the newly added built in nuget repository or else my builds failed because the build step was looking for the generated package under this repository and was not finding it.
" Searching for database package MyPackage version 0.22.31.6706 failed with error InvalidOperationException "

For your most recent error where the package version 0.20 for the package named BagheraData can't be found:

Yeh, that's our bad. It was caused because as of the most recent release of Deployment Manager it now has an embedded NuGet package feed, and we haven't yet done the work to make sqlCI compatible with it.

I'm going to get one of the developers to look into this urgently.

Detailed explanation:
To generate static upgrade scripts, sqlCI uses the DM API to ask which versions of the package are currently deployed to any environment in any project, and it then generates static upgrade scripts for those versions. To do this, it contacts the NuGet package feed to download those versions of the package in order to calculate the script.

The problem is that sqlCI only downloads packages from the first NuGet feed in DM no matter how many you have, and the embedded NuGet feed is always set to be the first one. What this means is that it tries to download the old version of the package from the wrong feed causing the error. We'll fix this in 2 ways:
1. We'll contact all the feeds in parallel.
2. We'll turn the package not being there into a warning rather than a build failure, since in the general case it might be an ancient version that got deleted from the NuGet feed, e.g. because TeamCity cleans up old versions after a while (depending on how you've configured it).

There is a temporary work around available for the later problem. As David suggested it is caused by the presence of the Deployment Manager package feed in version 1.1.0.27 if you already had an existing feed.

You can work around this problem by deleting this new feed. You can do this as follows:

1. In Settings > Package Feeds delete the Deployment Manager package feed. This is the embedded feed that was added in v1.1.

Just wanted to update this thread to let you know that we believe the problems detailed in David Simner's last post should be fixed in the latest version of SQLCI (v1.0.0.945) and the TeamCity Plugin (v1.0.0.1039).