3 ms·
> . Instead of needing to roll back a whole feature, you just roll back the commit which broke stuff. What if it's the whole feature that broke stuff? What if
by Aaargh20318 3y ago
> . Instead of needing to roll back a whole feature, you just roll back the commit which broke stuff.
What if it's the whole feature that broke stuff? What if we decide just before release that based on our release tests this particular feature isn't ready for production yet? Do you expect me to hunt through the entire commit log and identify and revert every single commit related to the feature?
- barrkel 3y agoNo, flip the feature flag. You have a feature flag because there's multiple commits for the feature and it can't be enabled until it's complete. And since you're continuously deploying, even if you did have to look for a commit, it wouldn't be more than a day or two old. Of course you wouldn't enable the feature all at once if at all possible. You'd do a canary first, sending a proportion of traffic. And your production system alerting would notice an elevated error rate on the canary and drain traffic to it, so you're not up in the middle of the night searching for a flag to flip or commit to roll back, at least not very often.