I agree I've never worked anywhere with really heavy duty CI, as in I've never worked somewhere that automated rollbacks were either trusted in all cases or business acceptable after something was production live. (Which is to say I haven't worked at places that had really significant scale.) And CI is only as good as your test coverage, which is to say if something esoteric is overlooked in your test suite...
Re:How to do a code review
by aledalgrande on Friday September 06, 2019 @09:55AM
(#20895644)
You are assuming that monitoring and rollback solutions are bug free, always on and have 100% knowledge of what's going on. That is never true.
The test of a good cd is that your ok with releasing on Friday at end of the day.