A software development practice in which developers merge their code changes into a shared repository frequently, with each merge automatically built and tested, so integration problems are caught early rather than accumulating.
Facts
Core Principlethe practice of integrating source code changes frequently and ensuring that the integrated codebase is in a workable state. 1 Connections
Sources
1. Continuous integration - Wikipedia
History section
Grady Booch first proposed the term CI in 1991, although he did not advocate integrating multiple times a day.
Introduction (lead section)
the practice of integrating source code changes frequently and ensuring that the integrated codebase is in a workable state.
View the SourceFrequently Asked Questions
Who first proposed the term continuous integration and did it originally mean merging several times a day?
Grady Booch proposed the term in 1991 without advocating several merges a day; that came later.
Grady Booch first proposed the term continuous integration in 1991. He did not advocate integrating multiple times a day, and that aspect was added to the practice later. The core idea, per the Wikipedia article on the subject, is integrating source code changes frequently and ensuring that the integrated codebase is in a workable state.
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.