29. Continuous Integration
Large software shops have been doing “nightly builds” for many years. The rationale is that team members work only on their own parts of the product. They can test their work and even fit it into the current state of the product. But the known-stable “current state” doesn’t reflect the latest efforts of the team, and the members’ development environment won’t match the production environment that will ultimately deliver the product.
What the team wants to know is whether their work fits together in a production environment, and on a variety of target devices. It does not want to wait for everyone to agree on a “stable” version of the code base; it wants to get the real, current mismatches diagnosed and fixed as soon ...
Get Xcode 5 Start to Finish: iOS and OS X Development 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.
