Deploy a Release step - No deployment targets available

[reece.walsh (Reece)]

Hi Rohin,

Thanks for getting in touch, I appreciate your patience.

In the deployment preview section, we show the machines that each step will execute on.

The Deploy Release step doesn’t execute on machines (as it runs on the Octopus Server) so it doesn’t show the target machines.

Whereas the Deploy Package step does execute on machines, so it will display each of the machines it’s going to run on.

This has been discussed in the following issue found here; I’d recommend having a look here for a breakdown.

Target nodes are not visable

No. Excluded machines will not flow through to the triggered child deployments. Unfortunately you are bumping into limitations of the feature. The Deploy Release step isn’t special from the point-of-view of the deployment page. I completely understand the behaviour you are expecting here. And we potential could display the deployment steps from child projects, and allow including\excluding machines from them. One potential issue is that there is no limit to how deeply these can be nested.…

A UserVoice suggestion (which is mentioned in the associated ticket) can be found below; I’d recommend leaving your vote and thoughts for this.

https://octopusdeploy.uservoice.com/forums/170787-general/suggestions/33710974-when-deploying-project-containing-deploy-release-s

I hope this helps!

If you require any further assistance or clarification, please let me know

Kind Regards,

Reece