Update 3/28/2012: In order to manage server configuration and code deployments, I’m experimenting with a free, hosted Chef account from OpsCode.com. I’m also following this blog post for the application deployment-specific questions and solutions.
My technical project for the year, I’ve decided, is to build a continuous delivery system inside the NUBIC dev team.
Here’s a quick reading list of source materials that I’m using to learn how to do it (blog posts to follow as I document the process of building the system internally):
- The Continuous Delivery book
- The Continuous Delivery blog
- Eric Ries’ 5-step primer to Continuous Deployment
- Case Study: Continuous deployment makes releases non-events
- IMVU’s Approach to Integrating Quality Assurance with Continuous Deployment
- A series on the principle of “The 5 whys”
- The Pareto principle, a.k.a. the 80/20 rule
These things couple very well with additional practices that NUBIC embraces as part of its software development process, including:
- Test Driven Development
- Behavior Driven Development
- Continuous Integration
- Releasing much of our code as open source
- Kaizen – continuous improvement philosophy
- Doing well on the “Joel Test”
Finally, ThoughtWorks Studios has a commercial product called Go for automated release management. A couple of people from ThoughtWorks also happen to be the authors of the book on Continuous Delivery.
No related posts.