Continuous Integration: Improving Software Quality and Reducing Risk -- Chapter 2, Introducing Conti

Continuous integration (CI) ensures the health of software by running a build with every change. Learn the advantages of CI and how to implement it in this excerpt from Continuous Integration: Improving Software Quality and Reducing Risk.

This Content Component encountered an error

As a registered member of SearchSoftwareQuality.com, you're entitled to a complimentary copy of Chapter 2 of Continuous Integration: Improving Software Quality and Reducing Risk written by Paul Duvall, Steve Matyas and Andrew Glover and published by Addison-Wesley Professional.

This chapter, "Introducing Continuous Integration," attempts to answer the questions that you may have when making the decision to implement the practices of CI on a project. It provides an overview of the advantages and disadvantages of CI, and covers how CI complements other software development practices.

CI is not a practice that can be handed off to a project's "build master" and forgotten about. It affects every person on the software development team, so the chapter discusses CI in terms of what all team members must practice to implement it.



Continuous Integration: Improving Software Quality and Reducing Risk

Book description:
For any software developer who has spent days in "integration hell," cobbling together myriad software components, Continuous Integration: Improving Software Quality and Reducing Risk illustrates how to transform integration from a necessary evil into an everyday part of the development process. The key, as the authors show, is to integrate regularly and often using continuous integration (CI) practices and techniques.

The authors first examine the concept of CI and its practices from the ground up and then move on to explore other effective processes performed by CI systems, such as database integration, testing, inspection, deployment, and feedback. Through more than 40 CI-related practices using application examples in different languages, readers learn that CI leads to more rapid software development, produces deployable software at every step in the development lifecycle, and reduces the time between defect introduction and detection, saving time and lowering costs. With successful implementation of CI, developers reduce risks and repetitive manual processes, and teams receive better project visibility.

This chapter is excerpted from the new book titled, Continuous Integration: Improving Software Quality and Reducing Risk, authored by Paul Duvall, Steve Matyas and Andrew Glover, scheduled to publish by Addison-Wesley Professional in late June, 2007. Copyright Pearson Education, Inc., ISBN 0321336380. For more information, please visit www.awprofessional.com.

>> Read "Introducing Continuous Integration" now.

>> Buy the book





This was first published in June 2007

Dig deeper on Software Quality Management

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

1 comment

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

-ADS BY GOOGLE

SearchSOA

TheServerSide

SearchCloudApplications

SearchAWS

SearchBusinessAnalytics

SearchFinancialApplications

SearchHealthIT

Close