Continuous Integration: Improving Software Quality and Reducing Risk (The Addison-Wesley Signature Series)
By P. Duvall, S. Matyas, Andy Glover. 2007
723 citations recorded by the source corpus.
View Paper: https://www.semanticscholar.org/paper/77e3051180623f0a5d0f859e28fce9078873cf22
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
- Bogdan Vasilescu
- Gregg Rothermel
- Leopold Talirz
- Sebastian G. Elbaum
- Stephen M. Schueller
- Brett K. Beaulieu-Jones
- David C. Mohr
- Snehal Kumbhar
Citations in the corpus
- The Behavioral Intervention Technology Model: An Integrated Conceptual and Technological Framework for eHealth and mHealth Interventions (2014, methodology): “Other aspects of the system related to software quality, such as reliability, security, maintainability, and efficiency, can be evaluated using software engineering metrics [38-40].”
- Quality and productivity outcomes relating to continuous integration in GitHub (2015, background): “Arguably, CI originated from the imperatives of agility [11], viz.”
- Reproducibility of computational workflows is automated using continuous analysis (2017, methodology): “Continuous analysis is an extension of continuous integration 16 , which is widely used in software development.”
- AiiDA 1.0, a scalable computational infrastructure for automated reproducible workflows and data provenance (2020, methodology): “On top of this quality control performed by peers, we have enabled an automatic continuous integration testing system 30 .”
- Techniques for improving regression testing in continuous integration development environments (2014, background): “In continuous integration development environments, engineers merge code that is under development or maintenance with the mainline codebase at frequent time intervals [8, 13].”