> Continuous Integration: “a software development practice where members of a team integrate their work frequently, usually each person integrates at least dail

> Continuous Integration: “a software development practice where members of a team integrate their work frequently, usually each person integrates at least daily,” says Martin Fowler. It generally involves running automated tests that run every time a patch is merged (“integrated”) into the repository’s main branch of code. I don't think it's about integrated patches into one piece of software, but rather about integrating the patched software into the entire software system in which it lives. So if you have three pieces of software (A, B & C) which are deployed together, they'll all live in the same repo (because multiple repos are almost always a mistake); each will have its own unit tests (because each piece of software is a unit); and then you'll have integration tests which test how well they play with one another, particularly when other folks are changing different parts of A, B & C at the same time. Fowler's article[0] reads like it could go both ways. I guess if you see any system of multiple processes as a single piece of software then it's much the same thing. [0] https://martinfowler.com/articles/continuousIntegration.html https://martinfowler.com/articles/continuousIntegration.html