000			03311cam a2200337 a 4500
008			100325s2007 njua b 001 0 eng
010			_a2007012001
020			_a9780321336385 (pbk. : alk. paper)
035			_a(Sirsi) u5618
040			_aEG-CaNU _c EG-CaNU _d EG-CaNU
042			_ancode
920			_a0321336380 (pbk. : alk. paper)
082	0	0	_a005 _2 22
100	1		_aDuvall, Paul M. _911144
245	1	0	_aContinuous integration : _b improving software quality and reducing risk / _c Paul M. Duvall with Steve Matyas and Andrew Glover.
260			_aUpper Saddle River, NJ : _b Addison-Wesley, _c c2007.
300			_axxxiii, 283 p. : _b ill. ; _c 24 cm.
490			_aAddison-Wesley signature series
500			_a"A Martin Fowler signature book"--Cover.
504			_aIncludes bibliographical references (p. 273-274) and index.
505			_aGetting Started 3 -- Introducing Continuous Integration 23 -- Reducing Risks Using CI 47 -- Building Software at Every Change 65 -- Continuous Database Integration 107 -- Continuous Testing 129 -- Continuous Inspection 161 -- Continuous Deployment 189 -- Continuous Feedback 203 --
520			_aFor 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 forty 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. The book covers * How to make integration a “non-event” on your software development projects * How to reduce the amount of repetitive processes you perform when building your software * Practices and techniques for using CI effectively with your teams * Reducing the risks of late defect discovery, low-quality software, lack of visibility, and lack of deployable software * Assessments of different CI servers and related tools on the market The book’s companion Web site, www.integratebutton.com, provides updates and code examples.
650	0		_aComputer software _x Quality control. _911145
650	0		_aComputer software _x Testing. _911146
650	0		_aComputer software _x Reliability. _911147
700	1		_aMatyas, Steve, _d 1979- _911148
700	1		_aGlover, Andrew, _d 1976- _91030
596			_a1
999			_c4624 _d4624