 - What is continuous integration (CI)?
Continuous integration (CI) is a software engineering practice in which isolated changes are immediately tested and reported on when they are added to a larger code base. The goal of CI is to provide rapid feedback so that if a defect is introduced into the code base, it can be identified and corrected as soon as possible. Continuous integration software tools can be used to automate the testing and build a document trail.
Continuous integration has evolved since its conception. Originally, a daily build was the standard. Now, the usual rule is for each team member to submit work on a daily (or more frequent) basis and for a build to be conducted with each significant change. When used properly, continuous integration provides various benefits, such as constant feedback on the status of the software. Because CI detects deficiencies early on in development, defects are typically smaller, less complex and easier to resolve.
According to Paul Duvall, co-author of Continuous Integration: Improving Software Quality and Reducing Risk, best practices of CI include:
-
Committing code frequently.
-
Categorizing developer tests.
-
Using a dedicated integration build machine.
-
Using continuous feedback mechanisms.
-
Staging builds.
CI originated from within the Extreme Programming paradigm but the principles can be applied to any iterative programming model, such as agile programming. Traditional development approaches, such as the waterfall model can benefit from using CI methods for the construction stage.
 |
Learn more about Extreme Programming (XP) |
| Better software through debugging and unit testing: Bugs plague software project big and small, and today's complicated software makes debugging more difficult than ever. Let these tips, tutorials, podcasts and articles help you. |
| Better software through debugging and unit testing -- Other useful resources: Here is a list of books, blogs and Web sites that can offer you more information on debugging, unit testing, XP and test-driven development. |
| Better software through debugging and unit testing -- Unit testing, Extreme Programming and TDD: Unit testing is a key element of Extreme Programming (XP) and test-driven development (TDD). These tips, tutorials and articles will help you further understanding unit testing. |
| Addressing software quality issues with development models, methods: Each development model has its own practices for building quality software. The challenge is determining which one fits your needs. The resources here can help you decide. |
| Clean Code: A Handbook of Agile Software Craftsmanship, Chapter 1 -- What Is Clean Code?: Agile software development calls on developers to write clean code, according to Robert "Uncle Bob" Martin. This free chapter introduces the concepts and methods of clean code. |
| LAST UPDATED: |
31 Jul 2008
|
 |
Do you have something to add to this definition? Let us know.
Send your comments to techterms@whatis.com
|
|
More resources from around the web:
|
 |
 |
| |
RELATED GLOSSARY TERMS
| Terms from Whatis.com − the technology online dictionary |
 |
Extreme Programming
(SearchSoftwareQuality.com)
Extreme Programming (XP) is a pragmatic approach to program development that emphasizes business results first and takes an incremental,...
|
|
JUnit
(SearchSoftwareQuality.com)
JUnit is an open source framework designed for the purpose of writing and running tests in the Java programming language... (Continued)
|
|
|
Show me everything on 
