As a part of our automation of standing up new EC2 windows servers within auto scaling groups, each new instance will run a PowerShell script that uses octo.exe to kick-off 4 different deployments (a, b, c & d). The octo.exe uses deploy-release to deploy to only that deployment target. In other words, target machine 1 deploys “a” to itself and target machine 2 deploys “a” to itself. Likewise for b, c and d.
However, when I look at these deployment tasks, “a” for target 2 queues up behind “a” for target 1. Likewise for the other deployment tasks. Why? The “a” deployments are going to different targets and can in no way interfere with each other.
I would like to make whatever change is possible to allow all these deployments (a, b, c & d) to deploy in parallel for every target machine launched by the auto scaling group. Is that possible? How?
I’ve attempted to reproduce this behavior on my end but could not cause anything definitive. Could you provide a copy of your Process JSON in order for me to more accurately reproduce the behavior?