I’ve recently started provisioning a new worker pool with a new worker in it running as an Azure VM with an Octopus Tentacle configured to be a worker (using “tentacle.exe register-worker”) to improve the deployment performance of some Azure-based steps. The idea is that running the scripts in an Azure VM-based worker means things will run at local Azure network speed rather than over our (slow / unreliable) ExpressRoute connection.
I think I’ve got everything more or less working and it seems to deploy ok, but I’m having some problems reading the UI for my process where it has child deployment steps - I can’t see where the worker config is defined in either the parent or child steps.
My two original steps looked like this:
When I added My Step 2 as a child step of My Step 1 the UI lost some of the information - what I see in each step is this:
Neither the parent nor child steps mention the “SI Worker Pool” once they’re nested, which makes it really hard to see what the deployment process will actually do.
Am I not looking in the right place, or is this information just not shown in nested steps? We’re on Octopus Deploy version “v2018.1.0.0 LTS” so I guess it’s possibly already been changed in a later version.