The DOI matches its Crossref record; 19 of the 22 references it cites were found in a registry or an index.
Continuous Integration and Continuous Delivery Pipeline Automation for Agile Software Project Management
Abstract
Agile practices with Continuous Integration and Continuous Delivery (CICD) pipeline approach has increased the efficiency of projects. In agile, new features are introduced to the system in each sprint delivery, and although it may be well developed, the delivery failures are possible due to performance issues. By considering delivery timeline, moving for system scaling is common solution in such situations. But, how much system should be scaled? System scale requires current system benchmark status and expected system status. Benchmarking the production is a critical task, as it interrupts the live system. The new version should go through a load test to measure expected system status. The traditional load test methods are unable to identify production performance behavior due to simulated traffic patterns are highly deviated from production. To overcome those issues, this approach has extended CICD pipeline to have three automation phases named benchmark, load test and scaling. It minimizes the system interruption by using test bench approach when system benchmarking and it uses the production traffic for load testing which gives more accurate results. Once benchmark and load test phases are completed, system scaling can be evaluated. Initially, the pipeline was developed using Jenkins CI server, Git repository and Nexus repository with Ansible automation. Then GoReplay is used for traffic duplication from production to test bench environment. Nagios monitoring is used to analyze the system behavior in each phase and the result of test bench has proven that scaling is capable to handle the same load while changing the application software, but it doesn't optimize response time of application at significant level and it helps to reduce the risk of application deployment by integrating this three phase approach as CICD automation extended feature. Thereby the research provides effective way to manage Agile based CICD projects.
Overview
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
Citations
Cites
Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation
Humble, J., & Farley, D. R. (2010) · Cited by 911
Shahin, M., Ali Babar, M., & Zhu, L. (2017) · IEEE Access · doi:10.1109/access.2017.2685629 · Cited by 680 · cited 2×
“CI servers provide centralized control over build tools and as per Shahin [15], Bamboo, Jenkins, Cruise Control, Hudson, Sysphus, Hydra, TeamCity are few available CI servers.”
BackgroundMethodAceto, G., Botta, A., de Donato, W., & Pescapè, A. (2013) · Computer Networks · doi:10.1016/j.comnet.2013.04.001 · Cited by 554
Continuous Delivery: Huge Benefits, but Challenges Too
Chen, L. (2015) · IEEE Software · doi:10.1109/ms.2015.27 · Cited by 261
Development and Deployment at Facebook
Feitelson, D. G., Frachtenberg, E., & Beck, K. L. (2013) · IEEE Internet Computing · doi:10.1109/mic.2013.25 · Cited by 243
Olsson, H. H., Alahyari, H., & Bosch, J. (2012) · 2012 38th Euromicro Conference on Software Engineering and Advanced Applications · doi:10.1109/seaa.2012.54 · Cited by 243
Alhamazani, K., Ranjan, R., Mitra, K., Rabhi, F., Jayaraman, P. P., Khan, S. U., Guabtni, A., & Bhatnagar, V. (2015) · Computing · doi:10.1007/s00607-014-0398-5 · Cited by 159
Continuous deployment at Facebook and OANDA
Savor, T., Douglas, M., Gentili, M., Williams, L. A., Beck, K. L., & Stumm, M. (2016) · ACM/IEEE International Conference on Software Engineering: Companion Proceedings (ICSE-Companion) · doi:10.1145/2889160.2889223 · Cited by 140
Microservices: Migration of a Mission Critical System
Mazzara, M., Dragoni, N., Bucchiarone, A., Giaretta, A., Larsen, S. T., & Dustdar, S. (2018) · IEEE Transactions on Services Computing · doi:10.1109/tsc.2018.2889087 · Cited by 129
On a Catalogue of Metrics for Evaluating Commercial Cloud Services
Li, Z., O’Brien, L., Zhang, H., et al. (2012) · doi:10.1109/grid.2012.15 · Cited by 118
Research works printed but not linked: 8
- kumbhar, 2015, Getting started with Continuous Integration in Software Development
- dunlop, 2015, DevOps: Are You Pushing Bugs to Clients Faster?, Proc of PNSQC
- 2016, Adopting Continuous Delivery, Continuous Delivery Whitepaper
- 2017, Compute Engine Management with Puppet, Chef, Salt, and Ansible | Solutions | Google Cloud Platform, Google Cloud Platform
- cunningham, 2017, Principles behind the Agile Manifesto, Agilemanifesto org
- 2017, Practicing Continuous Integration and Continuous Delivery on AWS
- cohn, 2015, Succeeding with Agile
- pulkkinen, 2013, Continuous Deployment of Software, Proc of the Seminar no 58312107 Cloud-based Software Engineering, 46
Cited by
Rangnau, T., Buijtenen, R. V., Fransen, F., & Türkmen, F. (2020) · IEEE International Enterprise Distributed Object Computing Conference (EDOC) · doi:10.1109/edoc49727.2020.00026 · Cited by 134
“Continuous Integration (CI) and Continuous Delivery (CD) are software engineering processes used in DevOps in order to improve the efficiency of projects [16].”
From DevOps to MLOps: Overview and Application to Electricity Market Forecasting
Subramanya, R., Sierla, S., & Vyatkin, V. V. (2022) · Applied Sciences · doi:10.3390/app12199851 · Cited by 89
“Continuous Delivery (CD) as a concept of the deployment pipeline [34].”
BackgroundDonca, I.-C., Stan, O. P., Misaroş, M., Gota, D.-I., & Miclea, L. C. (2022) · Sensors · doi:10.3390/s22124637 · Cited by 71
“CI/CD pipeline refers to planning strategy, development, and deployment [8].”
BackgroundContinuous Integration and Continuous Deployment Pipeline Automation Using Jenkins Ansible
Mysari, S., & Bejgam, V. (2020) · International Conference on Emerging Trends in Information Technology and Engineering (ICETITE) · doi:10.1109/ic-etite47903.2020.239 · Cited by 53
Ten quick tips for building FAIR workflows
de Visser, C., Johansson, L. F., Kulkarni, P., Mei, H., Neerincx, P. B. T., van der Velde, K. J., Horvatovich, P. L., van Gool, A. J., Swertz, M. A., Hoen, P. A. C. ’., et al. (2023) · PLoS Computational Biology · doi:10.1371/journal.pcbi.1011369 · Cited by 40
“CI refers to the automatic builds, tests, and integration of new code features, where CD means the automatic release of new software (versions), with the main developer’s approval [47].”
Method
Metadata
- Authors
- Arachchi, S. A. I. B. S., & Perera, I.
- Affiliations
- University of Moratuwa (LK)
- ORCID
- Perera, Indika
- Venue
- 2018 Moratuwa Engineering Research Conference (MERCon)
- Publisher
- IEEE
- Published
- 2018-05
- Pages
- 156-161
- OpenAlex
- W2887657564
- Cited by
- 97
- References
- 22
- Citations by year
- 2026: 8 · 2025: 13 · 2024: 17 · 2023: 18 · 2022: 20 · 2021: 14 · 2020: 6 · 2019: 1
- FWCI
- 4.34
- Type
- conference paper
- Language
- en
- Open access
- closed
- Locations
- Moratuwa Engineering Research Conference (MERCon) (publishedVersion)
- Topics
- Physical Sciences › Computer Science › Computer Networks and Communications › Software System Performance and Reliability
- Physical Sciences › Computer Science › Information Systems › Software Engineering Techniques and Practices
- Physical Sciences › Computer Science › Information Systems › Cloud Computing and Resource Management
- Keywords
- continuous integration and continuous delivery, load testing, system scaling, test bench, Jenkins, Ansible, response time
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Continuous Integration and Continuous Delivery Pipeline Automation for Agile Software Project Management. https://app.cochat.ai/papers/10.1109/mercon.2018.8421965
- The paper
- Arachchi, S. A. I. B. S., & Perera, I. (2018). Continuous Integration and Continuous Delivery Pipeline Automation for Agile Software Project Management. 2018 Moratuwa Engineering Research Conference (MERCon). https://doi.org/10.1109/mercon.2018.8421965
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.