Skip to main content

The importance of continuous integration

By Francisco Assis Rosa
Leading a team of developers in the effort of building a robust, quality software product should involve the establishment of some process and tools to assist the team effort and serve as a safety net for the errors of getting people to work together. Continuous integration is, I believe, a crucial element of that process. Introduced by Martin Fowler and Matt Foemmel (see article Continuous Integration), continuous integration establishes the practice of frequent integration of work developed by the several team members verified by automated build and testing of integrated code within a clean sandbox. This practice is valuable for several reasons:
  • It promotes the development of a clear process of building/deployment independent of any specificity of developer's platforms. Code that exists on a single platform only is bound to become dependent on specific aspects of that platform without anyone really noticing the dependencies until trying to port to other platforms. The existence of the integration clean sandbox allows these specific dependencies issues to not go unnoticed.
  • It promotes the development of testing. Being based on the premise of "test often" it makes the testing development part of the team's process. The fact that there is a platform built specifically for build and testing verification transforms, from the developer's perspective, testing efforts into an even more useful and justifiable effort.
  • It allows for quick detection of code integration issues by providing the clean slate for bringing all the code together. The little quirks of code combining can be detected by effective smoke/regression testing.
How hard is it to put in place continuous integration ? It depends a lot on where you are in your development process when you decide to take it up. If your team already makes use of build tools (e.g. Ant, Maven, even Make), makes use of a version control system (e.g. CVS, Subversion) and already does some kind of automated testing (e.g. xUnit) it can become pretty straightforward (You do use these don't you?!?). Continuous integration becomes simply a matter of setting up the integration sandbox and establishing the automation to detect changes in the version control system, building the changed system and testing the changes. You do not even need to go very far to accomplish that. You can find already systems that give you the continuous integration functionality that you need. At Tizra we have chosen to use the Cruise Control open-source, free framework for our continuous integration process (BSD-style license). It does pretty much what we need to do and keeps us on top of any integration issue that might arise from our development effort. It provides us unit tests results gathering, reporting and historical stats gathering for all checks. Continuous integration should be, in my opinion, an important practice for any serious software development company and I, for one, will make every effort to ensure it is put in place in every project I work with.
Labels:

Comments

Post a Comment

Popular posts from this blog

A Postcard from Tools of Change

By
Think back to the summer of 2007. The first iPhones are just hitting the stores. Kindle is still a gleam in Jeff Bezos' eye. And in the words of Publishers Weekly, "a festival of practical geekery" is taking place in San Jose, CA. That festival was the first Tools of Change for Publishing conference. We were there , of course. And while comparatively small, it was the largest gathering we'd found of people who cared as much as we did about the transition from print to digital books. That's still true today, which is why I'm excited to be on the floor of ToC 2010 as I write this. The show's a lot bigger now, and has spread beyond its geeky roots to focus on seismic shifts we're all aware of…the explosion of handheld devices , social software and changes in the ways all of us find and use information. If you're here, come see us. We'll be in booth 114 with our partners Digital Divide Data , and you can ...
Post a Comment
Read more

Kindle's Cool, but Remember the Web?

By Abe Dane
If anyone can obsolete the printed book, Amazon can, and they're clearly taking a formidable whack at it with their handheld Kindle reader. We can't help wondering, though, how many consumers will really pay $400 for a single-purpose reading device, when alternatives from a riotously competitive hardware market combine reading with phone, messaging, music and other capabilities. For example, the iPhone pictured here, with a tasty looking page delivered via Tizra's Agile PDF . We wish we could say it's the result of some special technology we came up with for delivering books to mobile devices, but really it's just a byproduct of the fact that Agile PDF makes books work like the web. So as the web finds its way into more mobile devices, so will books published with Agile PDF. Meanwhile, of course, there are already a billion or so eager readers accessing the web through more traditional means. By the way, the sesame crusted tuna's from Montreal's Aix Cui...
Post a Comment
Read more