Student or educator? Sign up with your school email and get 6 months of Pro free.
CoChat

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

Arachchi, S.A.I.B.S., Perera, Indika · 2018 · 2018 Moratuwa Engineering Research Conference (MERCon)

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

Crossref · 10.1109/mercon.2018.8421965

Cites

19 of 19 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Verification

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Citations

Cites

Show all 22 references

Research works printed but not linked: 8

  1. kumbhar, 2015, Getting started with Continuous Integration in Software Development
  2. dunlop, 2015, DevOps: Are You Pushing Bugs to Clients Faster?, Proc of PNSQC
  3. 2016, Adopting Continuous Delivery, Continuous Delivery Whitepaper
  4. 2017, Compute Engine Management with Puppet, Chef, Salt, and Ansible | Solutions | Google Cloud Platform, Google Cloud Platform
  5. cunningham, 2017, Principles behind the Agile Manifesto, Agilemanifesto org
  6. 2017, Practicing Continuous Integration and Continuous Delivery on AWS
  7. cohn, 2015, Succeeding with Agile
  8. pulkkinen, 2013, Continuous Deployment of Software, Proc of the Seminar no 58312107 Cloud-based Software Engineering, 46

Cited by

See all 97

Metadata

Authors
Arachchi, S. A. I. B. S., & Perera, I.
Affiliations
University of Moratuwa (LK)
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.