Continuous Integration


XP pairs integrate their code multiple times every day. Paradoxically, the more frequently you integrate, the easier it becomes. The longer you wait between integrations, the more changes have occurred since the last one. This results in more code conflicts between the working pairs, which makes the integration more difficult and more error prone. To accomplish continuous integration, the team must automate the integration process. That's a good thing.

Is Continuous Integration Essential?

To really accomplish small releases, you need the ability to build the system reliably and frequently. To support collective ownership, you need to avoid code conflicts. The more frequently you integrate, the fewer code conflicts you'll have.

Continuous integration isn't always easy. Once you figure out how to do it, it is always beneficial.



Extreme Programming Perspectives
Extreme Programming Perspectives
ISBN: 0201770059
EAN: 2147483647
Year: 2005
Pages: 445

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net