Continuous Integration: Improving Software Quality and Reducing Risk
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 cont...more
Paperback, 283 pages
Published
June 29th 2007
by Addison-Wesley Professional
Friend Reviews
To see what your friends thought of this book,
please sign up.
This book is not yet featured on Listopia.
Add this book to your favorite list »
Community Reviews
(showing
1-30
of
234)
The entire book can be reduced to two slides: one diagram and one bullet list of pros and cons. The diagram shows up again and again; they use it as a map to the contents, highlighting the current section. Each time, the diagram takes about three quarters of the page. It is not a very busy diagram and if could easily have
So far, it is very repetitive. They keep repeating the same things over and over. They keep promising that topics will be covered in more depth in later chapters, but I am stil...more
So far, it is very repetitive. They keep repeating the same things over and over. They keep promising that topics will be covered in more depth in later chapters, but I am stil...more
Good read. I liked the way the information is presented. I consider this to be a good complement to Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation but if I had to pick one, I'd select the CD book. Make sure to visit the companion website to get the most current recommendations.
Aug 03, 2011
Simon Parsons
added it
This is a general overview of CI, with examples from the java domain. There are no great revelations - but if you are new to CI, then it gives a good overview of the ideas
Let me be clear: I liked the information that was provided. Very useful and applicable to software engineering, and it really changed the way I look at development processes and continuous integration.
But it was way too wordy. I think the information could have been conveyed much more succinctly. The great nuggets of information were watered down with too many justifications and narratives and perspectives.
But it was way too wordy. I think the information could have been conveyed much more succinctly. The great nuggets of information were watered down with too many justifications and narratives and perspectives.
Jun 14, 2013
Mihai Criveti
marked it as to-read
May 24, 2013
Dan
marked it as to-read
May 13, 2013
Bryan
marked it as to-read
May 13, 2013
Hertzel Karbasi
added it
May 06, 2013
Vladimir Nikolov
marked it as to-read
Jun 05, 2013
Richard
added it
Apr 29, 2013
Alex
marked it as to-read
Apr 15, 2013
Juriekkigmail.com
added it
Apr 13, 2013
Katia
marked it as to-read
Apr 11, 2013
Henrique Gouveia
marked it as to-read
Apr 11, 2013
Dmitri Ragano
is currently reading it
There are no discussion topics on this book yet.
Be the first to start one »

Loading...

















