Tom Peters on 13 Oct, 2017 01:09 AM
Thanks for getting in touch.
With regards to automatic deployment to the QA environment, this should normally happen if the deployment to the previous phase completed successfully, even if there were warnings or errors. The important thing is that there were no errors that caused the deployment to fail.
Would you be able to attach the task log for the deployment that completed successfully, but with warnings or errors as described here? This will help us to narrow down what is causing those warnings or errors.
I have attached a full log (RAW) of the process . I have three questions now.
1. Why am i getting Warnings when there are no such in the log ?
2. Why do i get warnings only when i set QA to auto deployment in the lifecycle?
Last and the most important.
3. Why isn't my QA deployment getting triggered as soon as the Dev is sucessfully
completed, in spite of me setting the Life cycle to Auto-deploy for QA. Do i need to do something more for it to deploy automatically?
I think i found the reason for it not auto deploying to QA.
At the end of the attached log, there is following message
"Pending: Unable to trigger deployment for project 'AdiInsiteGlobal' release 20171013.1 to environment AdiInsite Global QA: AdiInsiteGlobal can only be deployed to tenants. Either deploy this release to a tenant, or configure this project to allow un-tenanted deployments. http://g.octopushq.com/MultiTenantProjectTenantRequired"
As i understand the message it is unable to find a Tenant when auto deploying to QA, which should not be the case. We do have Tenants in QA connected to this particular project .In fact when we promote the build from Dev to QA manually we go in for tenanted deployment as the project is configured for Tenanted deployments only.
Tom Peters on 13 Oct, 2017 06:32 AM
Unfortunately, this is a known issue with lifecycle auto deployments when you have a multi-tenanted project. You can read more about it and track our progress here.
As a workaround, are you able to initiate the deployments for both the Dev and QA environments from your CI build server?
So your build process could be:
2. Octopus: Create Release
3. Octopus: Deploy Release (Dev environment, specific tenant)
4. Octopus: Deploy Release (QA environment, specific tenant)
This should achieve the desired result.
Sorry you were hit by this bug! I'm hoping we can get it fixed sometime soon :)
Tom Peters on 13 Oct, 2017 07:38 AM
The "warning" for your deployment is the message you discovered at the end of the log:
Pending: Unable to trigger deployment for project 'AdiInsiteGlobal' release 20171013.1 to environment AdiInsite Global QA: AdiInsiteGlobal can only be deployed to tenants. Either deploy this release to a tenant, or configure this project to allow un-tenanted deployments. http://g.octopushq.com/MultiTenantProjectTenantRequired
So the fact that the deployment to the QA environment could not be done automatically caused a warning on the deployment to the Dev environment. This also explains why you only see the warnings after you have configured auto deployments in your lifecycle.