Continuous integration: Difference between revisions

Content deleted Content added
Replaced unorthodox reference by popular reference.
Replaced unorthodox reference by popular reference.
Line 88:
 
By committing regularly, every committer can reduce the number of conflicting changes. Checking in a week's worth of work runs the risk of conflicting with other features and can be very difficult to resolve. Early, small conflicts in an area of the system cause team members to communicate about the change they are making.
Committing all changes "at least once a day" (once per feature built) is generally considered part of the definition of Continuous Integration.<ref>{{cite book
|title=Continuous Integration: Improving Software Quality and Reducing Risk
|author1=Paul M. Duvall