Continuous integration is a software development practice in which developers merge their code changes into a shared repository frequently, often several times a day, with each merge triggering an automated build and test run that surfaces integration problems within minutes instead of at the end of a release cycle. This description is adapted from Wikipedia contributors under CC BY-SA 4.0; changes were made. https://creativecommons.org/licenses/by-sa/4.0/
Facts
Core PrincipleMerge every developer's changes into a shared codebase frequently, and let an automated build and test run catch integration problems within minutes instead of waiting for a release. 1 Origin YearGrady Booch used the term in his 1991 book on object-oriented design; the practice was later made a core Extreme Programming discipline by Kent Beck and given its now-standard description in Martin Fowler's 2000 essay. Connections
Sources
1. Continuous Integration (Wikipedia)
Wikipedia contributors, Wikimedia Foundationlead sentence
Continuous integration (CI) is the practice of integrating source code changes frequently and ensuring that the integrated codebase is in a workable state.
In Group: Software Development Processes, Introduction
Continuous integration (CI) is the practice of integrating source code changes frequently and ensuring that the integrated codebase is in a workable state.
View the Source Reader Challenges (0)
No disputes yet. Spotted an error or a better source? Open the first one.
Sign in to dispute this or suggest a correction.
View At A Past Year
Choose a year to see this entry's facts and connections as the atlas records them at that moment: what it held then, what it held instead, and what it had not yet adopted. Choose Present for the current record.