Allow releasing to a subset of servers under an environment
It'd be good to have the ability to release a package to a subset of servers under one environment. This would allow taking a server out of load, releasing to it, testing and then either flipping servers or putting it back in to load.
We usually do this when we have a large change or a change which needs a big DB migration.
Paul Zah commented
This has been in the PLANNED for a while now. Could we maybe get an rough ETA for it?
Regarding the canary concept, you don't necessarily need an additional config file. We just created a rule in our config manager to use prod config for prod-canary.
Callon Campbell commented
It would be great to have capability. We have multiple servers in our QA and Production environments. For our QA environment, we test multiple versions...prod support, current trunk and possible feature release branches. Because of this it would be nice to be able to specify which target agent to deploy to.
John Kent commented
When using an F5 load balancer it would be great to be able to disable a node from the pool, deploy new software onto it and then re-enable it back into the pool. Then continue this process for each of the nodes in the pool each corresponding to the various machines in the deployment environment.
This can currently be achieved like so:
You can pull out your single test server out into a "canary" environment, and deploy to that environment first, then deploy to a "production" environment which contains the other server.
I know that this would require you to make a "canary" config transform which is a copy of the "release" transform, but this should only be as much work as creating a separate config transform for each separate machine.
This is linked to this forum post: http://www.red-gate.com/messageboard/viewtopic.php?t=16300