In our testing in latest, this does work. You will need to have OctopusBypassDeploymentMutex on any projects you want this to work on scoped to the steps you want, and set to True.
If you have time to answer, can you please let me know the high level overview for the use case for this? It’s possible workers might fit better without the need for all the extra complexity and configuration.
We’re using large Octopus Projects that include steps for deploying web, services, applications and also database.
For the database steps, we are using a jumpbox (one tentacle that may connect to multiple database instances)
This requires us to use OctopusBypassDeploymentMutex in order to not queue up these projects that have a database step.
That is why we would like to scope the OctopusBypassDeploymentMutex variable , to only be used for specific tentacles (in our case the database deploys) and not for all other steps in a project.