or Create a profile
09 Feb, 2018 10:11 AM
There are a few reasons to be able to control the the target order in a rolling deploy. As I understand this order is now random, and with no possibility to control this.
One example where this would be useful is a situation we have experienced a couple of times:
Deployment steps look like this:
1. Disable webserver in Load Balancer (2 webservers in farm)
2. Deploy package
3. Warmup and test
4. Enable server in LB
So step 2 or 3 fails, and of course the server is not enabled in LB again. The reason for the error is corrected by the developer, and a new deploy is started. But now Octopus decides to start with the other webserver and disables that too in the LB (the first one is already disabled from the first run). Now both webservers are disabled and the site is basically down.
The developers don't have access to the LB and can't see or do anything about this.
If I somehow could tell Octopus to deploy using the same target order every time this situation would not occur.
Is it possible for me to achive this in any way, or do you have another solution for this?
on 12 Feb, 2018 02:09 AM
Thanks for getting in touch! At the moment the order is not deterministic and I created an issue to make it more explicit.
That being said I can see two approaches that can solve your problem in the meantime:
Please let me know how you go.
on 12 Feb, 2018 01:12 PM
Thanks for the reply!
1. If the deploy fails on a server that's out of the LB, it's not an option to include it again
2. This is of course possible (I didn't know about this), but it's still a manual step.
I endorse your issue "Make target order in rolling deployments deteministic"
Formatting help /
(switch to plain text)
(switch to Markdown)
You can attach files up to 10MB
If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.
A conversation has been started with the Octopus Deploy staff to resolve this discussion.
This discussion is private.
Only Octopus Deploy support staff and members of
can see and reply to it.
This discussion is public. Everyone can see and reply to it.
You can use Command ⌘ instead of Control ^ on Mac
Powered by Tender™.