As a software developer, you know that one of the critical period in a project is when you try to make integrate your code in the overall application and push it towards the final user. It is sometimes a long process that you would like to accelerate so that you could obtain a quicker feedback on the quality of your code. “Book Review: Continuous Integration: Improving Software Quality and Reducing Risk” is a book written by Paul Duvall, with Steve Matyas and Andrew Glover to help you improve the way you build and deliver software.
After a initial presentation of the continuous integration (CI) concepts and objectives, the content of the book goes far beyond the simple “continuous build” aspect to cover all disciplines concerned by CI: risk management, configuration management, database evolution, software testing, inspections, deployment. It is clear that CI is just not installing a suite of tools, but is mainly changing software development practices and process. Each chapter is well-structured with practical examples related to real life situations.
The book reach also nicely the objective of maintaining a balance between a somewhat tools- and language-neutral position, but still giving enough practical advice so that you could quickly adapt the advice to your own software development environment. Final appendixes give valuable information on CI resources and evaluating available CI tools.
Reference: Continuous Integration: Improving Software Quality and Reducing Risk; Paul M. Duvall, Steve Matyas, Andrew Glover; Addison-Wesley Professional
Thanks in favor of sharing such a nice opinion. This review about this continuous integration book is nice, thats why I have read it completely
Outstanding post on this continuous integration book, but I was wondering if you could write a litte more on this topic? I’d be very grateful if you could elaborate a little bit more.
Many thanks!