
DevOps and continuous integration/continuous deployment (CI/CD) automation
- 1 Saint Leo University
* Author to whom correspondence should be addressed.
Abstract
The rapid integration of DevOps and Continuous Integration/Continuous Deployment (CI/CD) has ushered in a transformative era in software development, streamlining processes and bolstering release efficiency. The amalgamation of development (Dev) and IT operations (Ops) into a cohesive DevOps model facilitates a more synergistic and responsive approach to the software lifecycle. Simultaneously, CI/CD automation accelerates the software release cadence, promising quicker feedback loops and more frequent feature releases. This paper delves into the underlying principles of DevOps and CI/CD, elucidating their collaborative benefits while also highlighting the associated challenges. Furthermore, the study assesses the impact of CI/CD on software quality, providing insights into best practices and potential future trends in the landscape of DevOps-driven software engineering.
Keywords
DevOps, continuous integration, continuous deployment, software lifecycle, automation
[1]. Bass, L., Weber, I., & Zhu, L. (2015). DevOps: A Software Architect's Perspective. Addison-Wesley Professional.
[2]. Debois, P. (2008). Agile Infrastructure and Operations: How infra-gile are you?. Agile 2008 Conference.
[3]. Duvall, P. M., Matyas, S., & Glover, A. (2007). Continuous integration: improving software quality and reducing risk. Addison-Wesley Professional.
[4]. Fitzgerald, B., & Stol, K. J. (2017). Continuous software engineering: A roadmap and agenda. Journal of Systems and Software, 123, 176-189.
[5]. Forsgren, N., Humble, J., & Kim, G. (2018). Accelerate: The Science of Lean Software and DevOps: Building and Scaling High Performing Technology Organizations. IT Revolution Press.
[6]. Humble, J., & Farley, D. (2010). Continuous delivery: reliable software releases through build, test, and deployment automation. Addison-Wesley.
[7]. Sharma, A., Sarkar, A., & Gupta, S. (2016). DevOps: Concepts, Affinities and Directions. SIGSOFT Softw. Eng. Notes, 41(2), 1-5.
[8]. Bellomo, S., Kruchten, P., Nord, R. L., & Ozkaya, I. (2014). How to Agilely Architect an Industrial Strength Financial System. IEEE Software, 31(2), 23-29.
[9]. Kim, G., Behr, K., & Spafford, G. (2016). The DevOps Handbook: How to Create World-Class Agility, Reliability, & Security in Technology Organizations. IT Revolution Press.
[10]. Loukides, M. (2012). What is DevOps?. O'Reilly Media.
[11]. Morrison, B., & Muehlhauser, C. (2018). Continuous Integration, Delivery, and Deployment: A Systematic Review on Approaches, Tools, Challenges, and Practices. IEEE Access, 6, 39089-39100.
[12]. Roche, J. (2015). Adopting DevOps Practices in Quality Assurance. Communications of the ACM, 58(11), 38-43.
Cite this article
Ali,J.M. (2023). DevOps and continuous integration/continuous deployment (CI/CD) automation. Advances in Engineering Innovation,4,38-42.
Data availability
The datasets used and/or analyzed during the current study will be available from the authors upon reasonable request.
Disclaimer/Publisher's Note
The statements, opinions and data contained in all publications are solely those of the individual author(s) and contributor(s) and not of EWA Publishing and/or the editor(s). EWA Publishing and/or the editor(s) disclaim responsibility for any injury to people or property resulting from any ideas, methods, instructions or products referred to in the content.
About volume
Journal:Advances in Engineering Innovation
© 2024 by the author(s). Licensee EWA Publishing, Oxford, UK. This article is an open access article distributed under the terms and
conditions of the Creative Commons Attribution (CC BY) license. Authors who
publish this series agree to the following terms:
1. Authors retain copyright and grant the series right of first publication with the work simultaneously licensed under a Creative Commons
Attribution License that allows others to share the work with an acknowledgment of the work's authorship and initial publication in this
series.
2. Authors are able to enter into separate, additional contractual arrangements for the non-exclusive distribution of the series's published
version of the work (e.g., post it to an institutional repository or publish it in a book), with an acknowledgment of its initial
publication in this series.
3. Authors are permitted and encouraged to post their work online (e.g., in institutional repositories or on their website) prior to and
during the submission process, as it can lead to productive exchanges, as well as earlier and greater citation of published work (See
Open access policy for details).