ThoughtWorks defines Continuous Integration as a development practice that requires developers to integrate code into a shared repository several times a day. By having a continuous process of building and deploying code, organizations are able to instill quality control and testing as part of the everyday work cycle. The result is that updates and bug fixes happen much faster and the overall quality improves.
- The advantages of Continuous Integration/Continuous Deployment
- from Getting Started with Kubernetes - Second Edition
- Publisher: Packt Publishing
- Released: May 2017
this paragraph doesn't prove the argument. Simply having Continuous Integration/Continuous Deployment processes does not lead to a better quality product. It can, with solid testing processes and practices in place, but it may not.
Share this highlighthttp://www.safaribooksonline.com/a/getting-started-with/9095936/