Been stuck on this for some time so any assistance would be useful. We are assessing Octopus and if we can’t get this to work it is unlikely that we will proceed with the product.
Thanks for getting in touch! It appears to have registered the correct packages for the release. So I would look at a) what feed you have setup in your feeds and if it is correctly connecting and finding those packages and b) in your package steps, is it set for the correct feed.
The --packages command just finds versions. It doesn’t upload the files or pre-download them, its assumed they are in a feed we have access to.
You need to define where Octopus can find your packages (where your package repository is). So if you are only seeing the Octopus Server, and you are using TeamCity NuGet feed then you need to add it there, otherwise you need to publish those packages to the Octopus Server repository. Here is the corresponding documentation page on how to setup your external feed: http://docs.octopusdeploy.com/display/OD/Package+repositories
I was under the mistaken impression that the Team City step: Octopus Deploy also had the responsibility of pushing the packages to Octopus’s Nuget library. Now I have this as a separate step all is good.
TeamCity has steps on build and package create that then can push to external feeds (such as ours) it can if its configured as such.
These videos are really in depth and show it all step by step: http://octopusdeploy.com/learn/videos
