Gated Check-in
Continuous integration (CI) identifies integration issues early by compiling (and testing) every time a change is committed to the workspace. This improves productivity by integration issues being found and resolved early, before too many developers are affected.
There is one fundamental issue with CI, and that is that if the integration fails the change has already been committed and any developers working in that workspace are impacted until the integration issues are resolved. In smaller teams this can be desirable because it acts as an impetus to get the issues resolved as quickly as possible, but as the size of the development team increases, the interruption while the issues are resolved may be unacceptable.
Gated check-in takes ...
Get Inside the Microsoft® Build Engine: Using MSBuild and Team Foundation Build now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
