3 ms·
How often are your features/fixes ready? How long does your testing take (this sets a lower bound)? How long is the deployment process (adds to that lower bound
by Jtsummers 8y ago
How often are your features/fixes ready? How long does your testing take (this sets a lower bound)? How long is the deployment process (adds to that lower bound)? How often does deployment have to be rolled back?
If testing takes a week, you can't get deploy less than weekly. Fix this, get your testing setup to the point where you have enough servers to hit your test instance(s) and get testing done fast (don't cut corners and remove tests).
If deployment takes days, work on getting that more automated so that it can happen more quickly and with less manual intervention. Write more deployment scripts/programs, and test them like you test your code.
If you're rolling back deployments, do an analysis of why. Was there an undetected bug? Why? Manual testing didn't catch it, make it automatic. Testing isn't comprehensive enough, check out other testing techniques like property based testing that can throw more cases at your system. Because the deployment process is manual and someone fat-fingered the wrong value? Move it into a configuration file and automate that step. Repeat.
Iterate on all of these things just like you iterate on the code for the system you're deploying. As you reduce the deployment and testing time (but not their correctness or completeness), you'll be able to get down to deployment times that are weekly or daily (or, in the ideal, continuously with each piece of code pushed to master).