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

Stanford's HighWire Press Picks Tizra

By
We're thrilled to announce a new partnership with Stanford University's HighWire Press.  It's exciting not only as an opportunity to work side-by-side with a longtime leader in online publishing, but also as validation of the robustness and flexibility we have worked so hard to build into Tizra.  HighWire has been serving up some of the most prestigious online journals in the world since 1995, and they are extremely selective about the technology they offer their customers. But the real proof of the collaboration's value is the response from the marketplace, with organizations including Project MUSE (Johns Hopkins University Press), Duke University Press , and GeoScienceWorld already signed on in advance of the product's launch.  Clearly, the increased discoverability, ease of use and agility resulting from the collaboration are what publishers—and readers—are looking for. Further details on the partnership are in the news release below.  A PDF version is ...
1 comment
Read more

Leave Web Enough Alone!

By Abe Dane
Jeremy Zawodny is rightly torqued about the needless complication of tools that purport to help with information sharing. The web's always had that pretty well covered, thanks to the simple magic of the URL. Anything you find, you can bookmark, email, or with a tinyurl , disseminate on a cocktail napkin. If my dear grandfather had been born later, he probably would never have picked up the habit of mailing articles lovingly clipped with a pen knife, and instead would have referred me to his del.icio.us feed. Zawodny points to a bizarre assortment of pop-ups, forms, and other unwelcome surprises that result from the "helpful" new sharing features, and notes... they seem to be placed on the sites under the assumption that I'm too stupid to send email (to the people I presumably email frequently already) with a URL in it... Thanks for the confidence boost. At Tizra, we're more inclined to say thanks to for the opportunity to do better. Our AgilePDF™ , for exampl...
Post a Comment
Read more

Context is King!

By
John Blossom's post on traditional portal strategies resonated with my recent thinking about aggregation sites ( Shorelines: portals Passe ). I made his post into a silly slogan for my subject line, but he is making a good case that even in the "piling things up" business, there are potential problems with actually piling them up. Reading it, for a minute, I had a pang about Tizra. You might be able to read it as saying that it's not worth building your own content collection at all, but I don't think that is the practical point for publishers. I think that the notion of stressing context and tuning product offerings to user groups is exactly what we enable with our product and content management tools. You need to have a branded presentation of your content to all your different audiences, and make every audience an offer that they want to buy. That takes a lot of flexibility, which is what we've concentrated on. That flexibility should be on tap, not the en...
Post a Comment
Read more