Continuous Integration has become a proven practice for improving software quality by ensuring that the codebase is _integrated_ (validated, compiled, and unit tested) on a _continuous_ (on check-in or scheduled) basis. It’s a great first step on the road to quality production code, but it’s just that: a first step. Beyond the gates of continuous integration lies a path filled with quality quagmires, from countless configuration files to database script disasters to deployment automation. While many developers will shrug their shoulders and say that it’s not their problem, the true professionals will not only take an interest in how their code makes it through production, but advocate for an end product that reflects the quality of their work. In this technology-neutral talk, we’ll explore how to take the foundation laid by continuous integration all the way through production, discuss how to deal with both the technical challenges and the people challenges (management, operations, etc), and show how a single developer can make a huge impact on the software development organization.
11th–13th January 2012