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.
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).
(internal reference numbers: