Skip to main content

The importance of continuous integration

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.

Comments

Popular posts from this blog

AppGap: Tizra more than just a "great tool for content sellers"

Bill Ives has been writing about knowledge management since the days when for most people that meant color coding your files, so we were really pleased when he agreed to evaluate Tizra Publisher in The AppGap , a blog on the future of work. We were even more pleased when he said "I see this service as a great tool for content sellers." But we thought his keenest insight was into applications beyond traditional publishing... [Tizra Publisher] can also be a useful content distribution system for enterprises that need to manage the presentation of their information. This will be especially useful for verticals with a lot of internal content such as legal firms, pharma, and other research oriented enterprises. Ives saw Tizra's combination of easy and yet precisely controlled content distribution as key for these users, and others needing to share marketing and technical information. Read the full review .

2018 Tizra User Summit: What We Learned by Meeting Our Customers Where We Are

They say you should "meet your customers where they are." Well, for Tizra 's 4th annual user conference we decided to take a chance and do the opposite. Instead of going to Chicago or DC, where Tizra customers are concentrated, we bet on hosting in our home town of Providence, RI. It's not that we don't love Chicago and DC, but we really felt we could do something special with the home field advantage. As it turns out, we were right. The Tizra user community is a silo-busting mix of creatives, technologists, content strategists and executives, who share the goal of building, engaging and generating value from audiences with digital content. For this crowd, we didn't want a sterile conference facility. We felt that by giving them a place they could really connect with, we'd help them connect with each other. Providence, with its vibrant tech and design scene, walkable downtown, and non-traditional venues, provided just the funky catalyst we were loo

Free Webinar: How to get off the mult-format content treadmill

Free Webinar: Friday, September 21 12-12:30 pm (ET) How to wrangle ALL your content types into one beautiful online hub… and get off the treadmill for good! It never lets up. First it was publications and conference materials. Then blogs and social media. Then webinars, infographics, podcasts and online courses. You keep cranking them out, but where do they all go? How can you keep your communications investment from evaporating at the speed of Twitter? Tizra lets you bring it all together into a great-looking, searchable, mobile-friendly website that delivers long-lasting value to your audience. In 30 minutes you will learn... How to broadcast and curate mixed media types for maximum impact. How to categorize content for ease of use and maintenance. How a well-tuned search can reveal hidden gems. REGISTER NOW!