Institutional-Repository, University of Moratuwa.  

Continuous integration and continuous delivery pipeline automation for agile software project management

Show simple item record

dc.contributor.author Arachchi, SAIBS
dc.contributor.author Perera, I
dc.contributor.editor Chathuranga, D
dc.date.accessioned 2022-09-01T06:06:56Z
dc.date.available 2022-09-01T06:06:56Z
dc.date.issued 2018-05
dc.identifier.citation S. A. I. B. S. Arachchi and I. Perera, "Continuous Integration and Continuous Delivery Pipeline Automation for Agile Software Project Management," 2018 Moratuwa Engineering Research Conference (MERCon), 2018, pp. 156-161, doi: 10.1109/MERCon.2018.8421965. en_US
dc.identifier.uri http://dl.lib.uom.lk/handle/123/18815
dc.description.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. en_US
dc.language.iso en en_US
dc.publisher IEEE en_US
dc.relation.uri https://ieeexplore.ieee.org/document/8421965 en_US
dc.subject continuous integration en_US
dc.subject continuous delivery en_US
dc.subject agile project management en_US
dc.subject version management en_US
dc.subject configuration management en_US
dc.title Continuous integration and continuous delivery pipeline automation for agile software project management en_US
dc.type Conference-Full-text en_US
dc.identifier.faculty Engineering en_US
dc.identifier.department Engineering Research Unit, University of Moratuwa en_US
dc.identifier.year 2018 en_US
dc.identifier.place Moratuwa, Sri Lanka en_US
dc.identifier.pgnos pp. 156-161 en_US
dc.identifier.proceeding Proceedings of 2018 Moratuwa Engineering Research Conference (MERCon) en_US
dc.identifier.email saibandara@gmail.com en_US
dc.identifier.email indika@cse.mrt.ac.lk en_US
dc.identifier.doi 10.1109/MERCon.2018.8421965 en_US


Files in this item

This item appears in the following Collection(s)

Show simple item record