3 ms·
I understand that continuous deployment could be very beneficial, but how do you change a customer from using US Army type deployment to accepting continuous de
by grogers 17y ago
I understand that continuous deployment could be very beneficial, but how do you change a customer from using US Army type deployment to accepting continuous deployment? What if you need to satisfy multiple different customers, all with their own taste or distaste for risks and new releases, how do you make the transition to continuous deployment?
It seems like crucial to the benefit of continuous deployment is that your code actually be used when you check it in by lots of people, so that regressions are found immediately. If you can't get that to happen, the entire process grinds to a halt.
- teej 17y agoI don't think continuous deployment necessitates deploying to production at the end. I worked at a startup that used continuous deployment to deploy to staging, then used push deployment to QA and to producion. This worked really well with the mostly-outsourced dev and QA teams. It gave rapid and concrete feedback to those teams, but left high risk operations in the hands of the dev lead and ops.