Do a step on a single target in a rolling deploy

Legacy Modelling
1

We have a webshop running on four frontend servers behind a load balancer.
To deploy to the servers we use a rolling deploy, that does the same steps on each target.

To make sure that nothing in the new code being deployed has broken the checkout, we do a manual test-order on the first target deployed to, before it’s returned to the load balancer. (We don’t always do this, most of the time we trust the automatic tests - but sometimes we want to make extra sure). To have this option, there are four manual intervention steps in each deploy, which makes deploys very un-automatic.

Because we only want to do this on the first target being deployed to, it would be nice to be able to specify a role, or target in the manual step. However it only allows for specific environments.

Is there a way to specify a step in a rolling deploy that only runs on one target?

2

Hi Secher,

Thanks for getting in touch! Unfortunately, there is no built in way for this to be done through Octopus. The only option we can think of would be a hack.

It would involve deploying twice, the first being the single target in each environment with a unique name for your script to check/perform tests on, then once confirmed you could deploy to the rest of the environments.

I know this is not ideal, however, we are unable to control which order targets are deployed to in a rolling deployment and stopping to test on a single target in a rolling deployment is not something Octopus is currently capable natively doing.

Please let me know if I have misread your situation. :slight_smile:

Best regards,
Daniel