Continuous Integration

Process

Description

Continuous Integration is a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily - leading to multiple integrations per day. Each integration is verified by an automated build (including test) to detect integration errors as quickly as possible. Many teams find that this approach leads to significantly reduced integration problems and allows a team to develop cohesive software more rapidly.

Martin Fowler at http://martinfowler.com/articles/continuousIntegration.html

Firms practicing Continuous Integration

  • 8
  • 4
  • Rubaidh

    We've toyed with a number of CI tools over the years to give us visibility of the state of our code bases. However, no matter which tool we use to give us that visibility, we are continually integrating code. Independent lines of development tend not to stray from the master branch for more than a day. Our current CI monitoring tool of choice is Atlassian's Bamboo. It's pretty awesome with Ruby (sometimes on Rails) projects.
    2
  • 3
  • 3
  • 3
  • Integrum

    All of our projects are in CruiseControl and displayed their status continually in the office.
    2
  • Microplace

    The development team integrates several times a day. We also have a monitor mounted on the wall, which runs a home-built screensaver to show the build status. The screensaver also displays the code coverage which oscillates between 98% and 99.5%.
    2
  • 1
  • 1
  • 1

Sponsored By