Klik op een omslag om naar Google Boeken te gaan.
Bezig met laden... Continuous Integration: Improving Software Quality and Reducing Risk (Martin Fowler Signature Books) (origineel 2007; editie 2007)door Paul M. Duvall, Steve Matyas, Andrew Glover
Informatie over het werkContinuous Integration: Improving Software Quality and Reducing Risk door Paul M. Duvall (2007)
Books Read in 2018 (2,860) Bezig met laden...
Meld je aan bij LibraryThing om erachter te komen of je dit boek goed zult vinden. Op dit moment geen Discussie gesprekken over dit boek. geen besprekingen | voeg een bespreking toe
Onderdeel van de uitgeversreeks(en)
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 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. Geen bibliotheekbeschrijvingen gevonden. |
Actuele discussiesGeenPopulaire omslagen
Google Books — Bezig met laden... GenresDewey Decimale Classificatie (DDC)005Information Computing and Information Computer programming, programs, data, securityLC-classificatieWaarderingGemiddelde:
Ben jij dit?Word een LibraryThing Auteur. |
CI is one of the fundamental underpinnings of group software development with any kind of reliability -- not just Agile. If you work in an environment where you need to create patches you need a properly managed version control system to begin with. If you want to be able to generate releases, or even move partial releases into a user acceptance testing environment, you need to be able to take the codebase on any given day and be ready, with reasonable confidence, to do a build and move it up the food chain -- which is why the continuous part of integration is so important. This book does a good job of showing, in addition to the technical underpinnings you need (in our environment it's mainly Jenkins, not namechecked in the book, but linked in the more up-to-date website associated with it), the sort of development culture and commitments you need to make CI work effectively. ( )