جمعه 15 بهمن 1395
نویسنده: Jeffrey Tamez
Continuous Integration: Improving Software Quality and Reducing Risk Andrew Glover, Paul M. Duvall, Steve Matyas
"Continuous Integration: Improving Software Quality and Reducing Risk" by Paul Duvall, Steve Matyas, Andrew Glover – Covers CI quite well from all possible angles. An interesting read on “Continuous Integration: Improving Software Quality and Reducing Risk” by Paul M. Luckily software engineering has developed the process of continuous integration designed to reduce wasted engineering effort. It's feels a even bit understatement to label it as continuous “deployment” because its advantages include improved productivity, increased customer satisfaction, reduced risk, decreased cost and better predictability and planning. The question then should be what is the value of the process as compared to the cost and risk? December 12, 2011 by pompermaier Leave a comment. It's no secret that most or all of Agile practices are aimed at reducing risk and improving the feedback cycle, right? We put our own twist on continuous integration by building into Bamboo build telemetry—Bamboo gives you heaps of metrics about your builds to help you see the big picture. By automating the software build process and providing instant notification of problems with the software's code, Bamboo helps development teams reduce project risk, improve productivity and enhance software quality. Risks in Continuous Integration. Continuous Integration reduces risk as integration problems are small (as small as the integration frame) and detected early (Of course, it's not the same to integrate 4 hours of work to integrating 3 days of work with a mainline that surely contains much more It helps reducing risk and improves feedback (which leads to a product with better quality). Eric Ries, co-founder and former CTO of IMVU, is a huge proponent of continuous deployment as a method of improving software quality due to the discipline, automation, and rigorous standards that are required in order to accomplish . Things that are traditionally not associated with Software quality assurance relies on short-cycle repetition and thoroughness which are easier to automate alongside with the deployment automation.