Continuous Integration, Delivery and Deployment: A Systematic Review on Approaches, Tools, Challenges and Practices

• Published in: IEEE access Vol. 5; pp. 3909 - 3943
• Main Authors: Shahin, Mojtaba, Ali Babar, Muhammad, Liming Zhu
• Format: Journal Article
• Language: English
• Published: Piscataway IEEE 2017; The Institute of Electrical and Electronics Engineers, Inc. (IEEE)
• Subjects: Bibliographies; continuous delivery; continuous deployment; Continuous integration; continuous software engineering; empirical software engineering; Engineering research; Fault detection; Flaw detection; Industrial development; Literature reviews; Organizations; Production; Reviewing; Software; Software development; Software engineering; State-of-the-art reviews; systematic literature review; Systematics; Testing; Visibility
• DOI: 10.1109/ACCESS.2017.2685629
• ISSN: 2169-3536

Continuous practices, i.e., continuous integration, delivery, and deployment, are the software development industry practices that enable organizations to frequently and reliably release new features and products. With the increasing interest in the literature on continuous practices, it is important to systematically review and synthesize the approaches, tools, challenges, and practices reported for adopting and implementing continuous practices. This paper aimed at systematically reviewing the state of the art of continuous practices to classify approaches and tools, identify challenges and practices in this regard, and identify the gaps for future research. We used the systematic literature review method for reviewing the peer-reviewed papers on continuous practices published between 2004 and June 1, 2016. We applied the thematic analysis method for analyzing the data extracted from reviewing 69 papers selected using predefined criteria. We have identified 30 approaches and associated tools, which facilitate the implementation of continuous practices in the following ways: (1) reducing build and test time in continuous integration (CI); (2) increasing visibility and awareness on build and test results in CI; (3) supporting (semi-) automated continuous testing; (4) detecting violations, flaws, and faults in CI; (5) addressing security and scalability issues in deployment pipeline; and (6) improving dependability and reliability of deployment process. We have also determined a list of critical factors, such as testing (effort and time), team awareness and transparency, good design principles, customer, highly skilled and motivated team, application domain, and appropriate infrastructure that should be carefully considered when introducing continuous practices in a given organization. The majority of the reviewed papers were validation (34.7%) and evaluation (36.2%) research types. This paper also reveals that continuous practices have been successfully applied to both greenfield and maintenance projects. Continuous practices have become an important area of software engineering research and practice. While the reported approaches, tools, and practices are addressing a wide range of challenges, there are several challenges and gaps, which require future research work for improving the capturing and reporting of contextual information in the studies reporting different aspects of continuous practices; gaining a deep understanding of how software-intensive systems should be (re-) architected to support continuous practices; and addressing the lack of knowledge and tools for engineering processes of designing and running secure deployment pipelines.