
Behaviorally speaking: Continuous Integration – managing chaos for quality!
Address
Bob Aiello raiello@acm.org
Bob Aiello - September 2003
Many CM practitioners work for large global companies where development teams can be as small as 10 developers or as large as hundreds spread out worldwide. My own work involves coordinating across numerous physical locations including the United States, Europe and Asia. Some developers need to work in isolation so we teach and support branching and merging of code. Otherwise their builds could break on a daily basis with significant loss of productivity. But this can obviously create some serious integration challenges that could potentially cause a critical project to fail. How can we make sense of this chaos and still secure our code? It should come as no surprise that these challenges highlight the value of CM and continuous integration is a key requirement for making all of this work.
Many CM practitioners work for large global companies where development teams can be as small as 10 developers or as large as hundreds spread out worldwide. My own work involves coordinating across numerous physical locations including the United States, Europe and Asia. Some developers need to work in isolation so we teach and support branching and merging of code. Otherwise their builds could break on a daily basis with significant loss of productivity. But this can obviously create some serious integration challenges that could potentially cause a critical project to fail. How can we make sense of this chaos and still secure our code? It should come as no surprise that these challenges highlight the value of CM and continuous integration is a key requirement for making all of this work.
Reviews (0)
Be the first to review this listing!
