Deployment Machine Index
Currently every step is running for every machine.
When you are deploying multiple machines, If you have a step that needs to run only one time per deployment like a global task for whole environment (for example; executing some database scripts before or after deployment.)
But we need to determine machine index to run some script only at first machine...
Regards, best wishes...
We have begun planning to provide some mechanism to allow for “Run step on N machines”, even when the roles map to multiple tentacles. The mechanism for selecting the machine that the deployment will run under is not yet clear.
Piers Williams commented
Rather than expose the 'machine index', I'd rather Octopus supported a native mechanism for limiting the number of times a deployment step can execute. I've raised this here: http://octopusdeploy.uservoice.com/forums/170787-general/suggestions/9569970-ability-to-globally-limit-number-of-times-a-step-w
The 'single tag' workaround is perfectly valid, but can be a pain depending on the fluidity of your environment (creates manual work where there should be none)
We achieve the same thing by tagging a single machine with a know tag.