There is no news flash: Continuous Integration is not new. It will, however, get a significant amount of attention during my upcoming tutorial session at the MySQL User Conference in April, where I am very pleased to be presenting Build and Release Management for Database Engineers.
I’m going to be talking about change management for databases. I’m going to talk about grouping sets of database changes together in unified releases. I’m going to talk about how these coordinate with changes in the applications that utilize your databases. I’m going to talk about how to fit your DDL, DML, views, triggers, routines and events into source control. Even more importantly, I’m going to talk about how to test these things. I’m going to talk about methods for creating multiple database instances to support application development staff without breaking the backs of your DBAs. I’m going to talk about automation. And then I’m going to talk about migrating your database changes logically through development to QA and then finally to production.
The bottom line: New tools such as MySQL Sandbox and Bazaar give us a chance to revisit release management, allowing us to come up with innovative ways to revise, automate, and streamline our processes. The result should be reduced hassle and increased confidence each time you have to release changes into your application’s production database.
Over the next few months, I’m going to be finalizing my presentation materials, and I’ll be posting my thoughts here. I’m sure there are a lot of people out there that have good experience in the subject matter. I welcome your comments and contributions.
One last small bit of housekeeping: I recently changed employment, and I am no longer working at Lotame Solutions, Inc. Although I have updated my profile information with the conference site, several pages are still showing my old company and my old bio. I am now a Database Developer at Bill Me Later, Inc., an eBay company.