It’s very easy to implement continuous integration as part of your enterprise agile transformation. Install some software and point it at your enterprise version control system. That box is ticked. But you just failed to implement CI. Why?
CI is a human process. Automated Continuous integration is meant to make it easier to implement that process. If you have developers who check in at the last possible minute, or who make the build green so they can pass all your enterprise quality gates and deploy, you aren’t doing CI. Sorry.
What use is a silver bullet anyway? Not much. Unless you use it to kill your NNPP.
Note: the Build Doctor and it’s contributors do not advocate shooting and/or killing any programmers. Or anyone else, for that matter.
(Image by dbking)
Related posts:
- Continuous Integration Quick Reference Continuous Integration is frequently written about. That’s all good. It’s...
- Continuous Integration Doom and Gloom? Andrew Binstock has written an article for SD Times, postulating...
- New Continuous Integration system I got a mail a few weeks ago from Mr...
- Continuous Integration Cage Fight: Buildforge This is the final (and very late) installment in the...
- The quest for a decent Ruby Continuous Integration tool Git has become very popular in the Ruby community. Github...
Related posts brought to you by Yet Another Related Posts Plugin.
{ 2 comments… read them below or add one }
Absolutely right.
James Shore covered this a while back: Continuous Integration is an Attitude Not a Tool.
@jtf: I just ‘fessed up to James. Thanks for pointing that out. Somehow I missed that one.