Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation

By Jez Humble, D. Farley. 2010

1,256 citations recorded by the source corpus.

How researchers see this paper

The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.

Continuous Integration, Delivery and Deployment: A Systematic Review on Approaches, Tools, Challenges and Practices (2017, background): “…Research Organisation, Sydney, NSW 2015, Australia mojtaba.shahin@adelaide.edu.au, ali.babar@adelaide.edu.au, liming.zhu@data61.csiro.au Abstract—Context: Continuous practices, i.e., continuous integration, delivery, and deployment, are the software development industry practices that…”
Quality and productivity outcomes relating to continuous integration in GitHub (2015, background): “In software engineering, continuous integration is viewed as a paradigm shift, “perhaps as important as using version control” [22].”
Robust log-based anomaly detection on unstable log data (2019, background): “This is especially important for organizations that adopt the Continue Delivery/Deployment approaches [6, 22].”
A Survey of DevOps Concepts and Challenges (2019, background): “In the Continuous Delivery book [82], Humble advocates for an automated deployment pipeline , in which any software version committed to the repository must be a production-candidate version.”