We have TeamCity pushing a package to Octopus 3.11.1 via octo.exe. We have automatic release creation enabled on the project, which is firing correctly. We have the default lifecycle with only one environment in it, with one tenant from that environment tied to the project. As in Dalmiro’s comment 2 from http://help.octopusdeploy.com/discussions/questions/5753-automatically-deploying-a-release, the default lifecycle is set to deploy automatically to this environment as soon as the release enters this phase. However, after the release is automatically created, the lifecycle never fires, and no deployment is made.
We currently do not support auto-deploy environments for projects that require a Tenant, we have this GitHub issue to support this scenario.
In the meantime the above issue has a workaround that should hopefully get you up and running again.
The screenshot on the docs page looks to be out-of-date as the Deployment target is available for deployment has been renamed to Machine becomes available for deployment.
The workaround worked for us, thank you. TeamCity is now deploying to the tenant.
I would like to up-vote sarbis’ comment on that issue, as we would like to eventually have the ability to filter tenants for auto-deploy. The separation of concerns is also ideal, of course.
Thanks for continuing to produce such a great product!
