To see the other types of publications on this topic, follow the link: Continuous Integration/Continuous Delivery (CI/CD).
Journal articles on the topic 'Continuous Integration/Continuous Delivery (CI/CD)'
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the top 50 journal articles for your research on the topic 'Continuous Integration/Continuous Delivery (CI/CD).'
Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.
You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.
Browse journal articles on a wide variety of disciplines and organise your bibliography correctly.
1
Sharma, Vandana. "Continuous Integration and Continuous Delivery (CI/CD): A Comprehensive Overview." International Journal of Science and Research (IJSR) 8, no. 10 (2019): 1835–39. http://dx.doi.org/10.21275/sr24115221653.
Full text
2
Dachepally, Raju. "Continuous Integration and Continuous Delivery (CI/CD) Pipelines: Best Practices for Modern Enterprises." INTERANTIONAL JOURNAL OF SCIENTIFIC RESEARCH IN ENGINEERING AND MANAGEMENT 05, no. 10 (2021): 1–8. https://doi.org/10.55041/ijsrem10912.
Full textAbstract:
Continuous Integration (CI) and Continuous Delivery (CD) pipelines have become indispensable for modern enterprises aiming to achieve agile and scalable software development. This paper explores best practices for designing and implementing robust CI/CD pipelines, focusing on efficiency, security, and scalability. Key strategies include automated testing, pipeline as code, and integrating security measures. The paper features diagrams, flowcharts, and pseudocode to provide actionable insights. Future trends and challenges in CI/CD adoption are also discussed. Keywords CI/CD Pipelines, Automation, DevOps, Continuous Integration, Continuous Delivery, Pipeline as Code, Agile Development, Secure Software Development Lifecycle
3
Akilnath, Bodipudi. "Integrating Vulnerability Scanning with Continuous Integration/Continuous Deployment (CI/CD) Pipelines." European Journal of Advances in Engineering and Technology 9, no. 2 (2022): 49–55. https://doi.org/10.5281/zenodo.13622978.
Full textAbstract:
In the era of DevOps, the integration of Continuous Integration and Continuous Deployment (CI/CD) pipelines has revolutionized the software development lifecycle, ensuring rapid and reliable delivery of applications. However, this accelerated development pace introduces significant security challenges, particularly in maintaining the security posture of local servers. This paper investigates the integration of vulnerability scanning into CI/CD pipelines, aiming to enhance the security of applications and underlying infrastructure throughout the development process. We explore various vulnerability scanning tools and techniques, assess their efficacy within CI/CD environments, and propose best practices for seamless integration. The study also includes a case analysis of a real-world implementation, demonstrating the practical benefits and challenges of incorporating vulnerability scanning in CI/CD pipelines. Our findings underscore the importance of early and continuous vulnerability detection, fostering a proactive security culture in DevOps practices.
4
Swetha, Sistla. "The Evolution of Continuous Integration – Continuous Delivery." International Journal of Innovative Research in Engineering & Multidisciplinary Physical Sciences 9, no. 4 (2021): 1–7. https://doi.org/10.5281/zenodo.14261017.
Full textAbstract:
CI/CD has been instrumental in changing the way developers used to work with software; this evolution allowed the delivery of code changes faster and in a more reliable way. In this whitepaper, take a look at how Continuous Integration and Continuous Delivery work within a historical context, their present state, and trends for the future, as well as how the integration of both disciplines has shaped modern DevOps environments. What began as a series of separate practices for integrating the code and deploying it, respectively, grew into one discipline whereby all those aspects got automated towards software delivery. Automating the most critical software lifecycle stages-from integrating the code and testing to deploying and monitoring-software delivery, the CI/CD pipelines attain collaboration, increase development velocity, and reduce release risk.
5
Harish Chakravarthy Sadu. "Demystifying continuous integration and continuous deployment for enterprise web applications." World Journal of Advanced Engineering Technology and Sciences 15, no. 3 (2025): 1122–29. https://doi.org/10.30574/wjaets.2025.15.3.1024.
Full textAbstract:
This article demystifies Continuous Integration and Continuous Deployment (CI/CD) practices within enterprise web application development. It traces their evolution from experimental approaches to essential frameworks driving software delivery excellence. The article explores foundational concepts, architectural patterns, implementation strategies, and resilience mechanisms that help organizations balance rapid delivery with system stability. It covers critical aspects including database migration strategies, multi-service coordination, chaos engineering techniques, and performance metrics that determine CI/CD effectiveness. Through analysis of real-world applications across financial reporting, supply chain management, and analytics domains, it provides a practical roadmap for enterprises implementing CI/CD pipelines. By addressing both technical and business dimensions, it shows how proper CI/CD implementation delivers accelerated time-to-market, enhanced product stability, and improved operational resilience in environments where deployment failures carry significant consequences.
6
Prayag, Ganoje. "Continuous Integration and Deployment Pipelines." Journal of Scientific and Engineering Research 7, no. 3 (2020): 324–27. https://doi.org/10.5281/zenodo.13752931.
Full textAbstract:
This research paper explores the principles and best practices of Continuous Integration (CI) and Continuous Deployment (CD) pipelines, focusing on their application in the development of medical device software. As the healthcare industry increasingly relies on software-driven medical devices, ensuring efficient and reliable software delivery is paramount. This paper examines the key components of CI/CD pipelines, discusses best practices for implementation, and presents case studies of successful CI/CD strategies in the medical device industry. The paper also addresses common challenges, potential pitfalls, and future trends in CI/CD for medical device software development.
7
Nagaraju Thallapally. "Implementing continuous integration and continuous deployment (CI/CD) pipelines." International Journal of Science and Research Archive 3, no. 2 (2021): 248–53. https://doi.org/10.30574/ijsra.2021.3.2.0073.
Full textAbstract:
Continuous Integration (CI) and Continuous Deployment (CD) are fundamentals of today’s software development to deliver quality code, deliver faster, and reduce the cost of deployment. Automation of integration and deployment helps teams find the faults before they are found and eliminate manual effort during the development lifecycle with CI/CD pipelines. This article talks about the main parts of CI/CD pipelines, their benefits, best practices, and the tools available to help them. We also cover common organizational barriers to CI/CD implementation and give you solutions for how to overcome them. We also share case studies and the future of CI/CD.
8
Jaeni, Jaeni, Nicko Aji S., and Arif Dwi Laksito. "IMPLEMENTASI CONTINUOUS INTEGRATION/CONTINUOUS DELIVERY (CI/CD) PADA PERFORMANCE TESTING DEVOPS." Journal of Information System Management (JOISM) 4, no. 1 (2022): 62–66. http://dx.doi.org/10.24076/joism.2022v4i1.887.
Full textAbstract:
Secara umum proses pengembangan aplikasi terdiri dari proses perancangan, pengujian, dan deployment. Pengembangan dengan cara tradisional seringkali menimbulkan masalah seperti keterlambatan aplikasi dan kualitas produknya. Hal ini dapat terjadi karena tim operasional harus menunggu developer agar menyelesaikan proses uji coba terlebih dahulu sebelum aplikasi tersebut dapat dirilis dan diguankan. Selain itu, setelah proses pengujian selesai, sering didapati adanya konflik akibat environment yang berbeda, yang memperlambat proses rilis. Keterlambatan ini membuat klien kecewa dan memberikan efek yang tidak baik bagi perusahaan. Continuous Integration / Continuous Delivery (CI/CD) dapat dijadikan solusi untuk memecahkan masalah ini. CI/CD dapat menjadi jembatan antara tim pengembang dan tim operasional.. Kata Kunci: Continuous Integration, Continuous Delivery, Gitops, Perfomance testing
9
G., Singaravel, Sethupathi S., and Satheshkumar T. "Continuous Integration and Continuous Delivery (CI/CD) in Agile Development: Implementation Strategies and Benefits." Bonfring International Journal of Man Machine Interface 15, no. 1 (2025): 1–3. https://doi.org/10.9756/bijmmi/v15i1/bij25001.
Full textAbstract:
Continuous Integration and Continuous Delivery (CI/CD) practices are proven essential foundations for the realization of Agile ideals in the field of software development. Though CI/CD is widely recognized for its potential gains regarding shortened development cycles, increased code quality, and improved team collaboration, management of CI/CD in Agile environments is still problematic. The research wants to study the following key research questions: a) What are the most effective strategies for implementing CI/CD in agile development teams? b) What are the perceived advantages and difficulties in adopting CI/CD practices in agile projects? c) How does the integration of CI/CD affect the speed, code quality, and productivity of development in agile environments? d) What are the critical success factors and best practices to maximize the benefits of CI/CD in Agile development? The research aims to provide empirical studies, case analyses, and interviews with industry practitioners in relation to the questions for meaningful actionable insights and recommendations on how CI/CD implementation strategies can best be maximized and what can be done to harness the full power of CI/CD in Agile development contexts [1],[12]. Such insights will help advance the field of practice and software development methodologies in rapidly evolving digital landscapes.
10
Praveen, Kumar Koppanati. "Implementing Dynamic Environments with GitLab CI/CD." European Journal of Advances in Engineering and Technology 9, no. 12 (2022): 175–79. https://doi.org/10.5281/zenodo.13912547.
Full textAbstract:
Dynamic environments have become essential in modern software development, allowing developers to test, stage, and deploy applications in a reliable, repeatable, and isolated manner. GitLab CI/CD offers a robust framework to build, deploy, and manage dynamic environments that scale with the needs of both small and large development teams. This paper explores the implementation of dynamic environments using GitLab CI/CD, discussing key practices, the architecture of GitLab's Continuous Integration and Continuous Deployment (CI/CD) pipeline, and methodologies for automating testing, deployment, and scaling. Drawing on the existing academic literature and case studies, this paper also delves into the integration of infrastructure as code (IaC) with GitLab CI/CD, effective environment branching, and best practices in the continuous delivery of applications. We focus particularly on dynamic environments' role in improving DevOps efficiency and reducing the risks associated with manual deployments.
11
Ratnangi, Nirek. "Impact of Continuous Integration and Continuous Deployment (CI/CD) on Software Quality and Delivery Speed in Linux Systems." European Journal of Advances in Engineering and Technology 6, no. 8 (2019): 95–99. https://doi.org/10.5281/zenodo.13919415.
Full textAbstract:
Continuous Integration (CI) and Continuous Deployment (CD) have become pivotal processes in modern software development, aiming to enhance software quality and expedite delivery. By evaluating case studies, reviewing literature, and analyzing industry reports, we explore how CI/CD processes enable automated testing, frequent code integration, and rapid deployment. Furthermore, we assess how these practices affect key metrics such as defect detection, time to market, and system stability in Linux environments, where open-source software development practices dominate. The findings highlight that CI/CD pipelines improve software quality by fostering early bug detection and reduce delivery time through automation. However, they also pose challenges in terms of infrastructure complexity and security vulnerabilities. This paper concludes by recommending best practices for implementing CI/CD in Linux-based projects to maximize the benefits while mitigating the risks.
12
Prasad Pasam, Thulasiram. "Optimizing Code Efficiency within Continuous Integration and Continuous Delivery Systems." International Journal of Engineering and Science Invention 10, no. 2 (2021): 57–62. https://doi.org/10.35629/6734-10025762.
Full textAbstract:
This study focuses on methods to improve the speed of Continuous Integration and Continuous Delivery (CI/CD) systems. Using a secondary qualitative approach, the study looks at code refactoring, modular programming, task parallelism, and caching. The themes discover the reasons these approaches benefit build efficiency, testing performance, and dependable deployment. It describes actual examples and finds a lack of standardised structures in practice. Drawn from interpretivist philosophy, this research gives a clearer view of code-related boosts in CI/CD and forms the base for future intelligent, automated studies of software delivery.
13
Namsraidorj, Munkhtsetseg, Sanchirjav Lkhaasuren, Bagabold Gendensuren, Khantulga Radnaa, Javkhlan Rentsendorj, and Amirlan Enkhtur. "Continuous Integration and Delivery of Software products: Pipeline implementation." International Journal of Engineering and Computer Science 13, no. 05 (2024): 26172–77. http://dx.doi.org/10.18535/ijecs/v13i05.4821.
Full textAbstract:
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. CI/CD is the best practice for teams using a DevOps methodology and is best suited to agile methodologies. CI/CD automates code integration and delivery, allowing software development teams to focus more on business requirements. Implementing CI/CD and automating the delivery process from application development to the live environment using pipelines, reducing the time and errors during manual delivery, the previously mentioned high-quality and reliable software products are delivered to the end user. This work will automate the workflow of software products from development to supply and delivery using pipelines.
14
Vamsi, Krishna Thatikonda. "Beyond the Buzz: A Journey Through CI/CD Principles and Best Practices." European Jornal of Theoretical and Sciences 1, no. 5 (2023): 334–40. https://doi.org/10.59324/ejtas.2023.1(5).24.
Full textAbstract:
Continuous Integration and Continuous Deployment (CI/CD) are pivotal in modern software development. Shifting from the classic waterfall models, the current age is dominated by Agile methodologies and DevOps practices. This article explores CI and CD's core principles, differences, and similarities. It touches upon essential techniques such as automation, ensuring consistency, and the importance of quick feedback mechanisms. Beyond these, the discussion extends to cutting-edge methods, infrastructure as code, potential security considerations, and monitoring within CI/CD environments. While CI/CD offers numerous benefits, it's essential to acknowledge its challenges, which necessitate attention and action. With an ever-evolving landscape featuring trends like AI/ML integration into CI/CD, businesses find themselves at a juncture where embracing and finetuning CI/CD is vital for competent software delivery.
15
Khan, Abdul, Aman Shaikh, Imran Tadwal, Yash Bhadkumbe, and Prof S. A. Nandi. "Continuous Integration, Continuous Delivery Pipeline with AI Integration." INTERANTIONAL JOURNAL OF SCIENTIFIC RESEARCH IN ENGINEERING AND MANAGEMENT 08, no. 11 (2024): 1–7. http://dx.doi.org/10.55041/ijsrem39159.
Full textAbstract:
In today’s fast-paced tech world, dropping apps quickly while keeping them top-tier is non-negotiable. This project dives into fixing the grind of traditional, error-prone software development by rolling out a Continuous Integration and Continuous Deployment (CI/CD) pipeline on Amazon Web Services (AWS). The idea is simple: ditch the old-school manual hustle and use automation tools to totally revamp the software game. From coding to deployment, everything gets faster, smarter, and way more reliable—no more messy releases or unnecessary delays. Back in the day, manual processes were a total buzzkill for development teams. Code integration took forever, testing was a headache, and deployments were straight-up chaos, leading to bugs and downtime. As apps got bigger and more complex, these issues only stacked up, slowing down the entire system. Our project uses AWS tools like CodePipeline, CodeBuild, and CodeDeploy to sort this out. These tools handle code integration, testing, and deployment on autopilot, speeding up the delivery game while cutting down on human errors. Plus, QA teams can breathe easy with less grunt work, and developers can focus on creating cool features instead of firefighting bugs. On top of being faster and more accurate, this pipeline levels up teamwork with instant feedback on code changes. Developers can squash bugs on the fly, and everyone from project managers to stakeholders stays in the loop about what’s going down. This creates a vibe of constant improvement—each update builds on the last, making the software sharper every time. Thanks to AWS’s scalable setup, handling bigger projects or adding more team members is no biggie. It’s like having a system that grows with you without ever feeling clunky. And let’s not forget how this aligns perfectly with modern DevOps goals. By automating repetitive and boring tasks, teams can focus on the stuff that actually matters, like innovation and problem-solving. With AWS’s rock-solid tools, security and performance stay on point, no matter how hectic things get. This project is proof that tech done right can help teams stay ahead of the curve and deliver epic software that meets today’s high standards. Key Words: AWS CI/CD Pipeline, AWS CodeCommit, AWS CodeBuild, AWS CodeDeploy, AWS CodePipeline, Amazon Elastic Beanstalk
16
Kulanov, V., and A. Perepelitsyn. "Method of Creation of FPGA Projects Using Continuous Integration and Continuous Delivery Technology." Èlektronnoe modelirovanie 47, no. 2 (2025): 92–107. https://doi.org/10.15407/emodel.47.02.092.
Full textAbstract:
The reasons of increasing the demand for the use of Field Programmable Gate Array (FPGA) are analyzed. The use of hardware description languages and project creation processes is con-sidered. The possibility of using continuous integration and continuous delivery (CI/CD) tech-nology for creation of FPGA projects is established. The fundamental stages of creating FPGA projects using hardware description languages are analyzed. Existing tools of automation and CI/CD for project creation are analyzed. The model of the process of creation of FPGA pro-jects using CI/CD technology is presented. The sequence of steps for integrating CI/CD tech-nology for the process of creation of FPGA projects is proposed. A detailed explanation of the process of applying the proposed sequence of steps of creation of FPGA project using CI/CD technology is proposed. A practical example of the application of the proposed method in the educational process is provided. The main contribution of this work is to simplify the process of creating a system that provides a visual and accessible code quality check, as well as allows to identify problematic areas in the code written with the help of hardware description lan-guages. To achieve that the modern technologies of continuous integration and continuous de-livery are utilized.
17
Singh, Chandra Prakash. "The Role of RPA in Transforming DevOps: Driving CI/CD Efficiency and Beyond." INTERANTIONAL JOURNAL OF SCIENTIFIC RESEARCH IN ENGINEERING AND MANAGEMENT 09, no. 01 (2025): 1–6. https://doi.org/10.55041/ijsrem8160.
Full textAbstract:
The COVID-19 pandemic has profoundly reshaped the global business environment, compelling organizations to accelerate their digital transformation journeys. Remote work has become the standard, fueling an unprecedented demand for swift and dependable software delivery. This white paper delves into how Robotic Process Automation (RPA) can revolutionize DevOps practices, particularly through the automation of Continuous Integration and Continuous Deployment (CI/CD) pipelines. By integrating RPA, organizations can eliminate manual bottlenecks, enhance accuracy, and scale their software delivery processes effectively. Keywords Robotic Process Automation (RPA), DevOps Automation, Continuous Integration (CI), Continuous Deployment (CD), CI/CD Pipelines, Digital Transformation, Remote Work Efficiency, Real-Time Testing, Error Reduction, Process Scalability, Compliance Automation, Labor Optimization, Cost Efficiency, Workflow Automation, Incident Management Automation
18
Alanda, Alde, Hanriyawan Adnan Mooduto, and Rizka Hadelina. "Continuous Integration and Continuous Deployment (CI/CD) for Web Applications on Cloud Infrastructures." JITCE (Journal of Information Technology and Computer Engineering) 6, no. 02 (2022): 50–55. http://dx.doi.org/10.25077/jitce.6.02.50-55.2022.
Full textAbstract:

 At this time, the application development process has experienced much development in terms of tools and the programming language used. The application development process is required to be carried out in a fast process using various existing tools. The application development and delivery process can be done quickly using Continuous Integration (CI) and Continuous Delivery (CD). This study uses the CI/CD technique to develop real-time applications using various programming languages implemented on a cloud infrastructure using the AWS codepipeline, which focuses on automatic deployment. Application source code is stored on different
 media using GitHub and Amazon S3. The source code will be tested for automatic deployment using the AWS code pipeline. The results of this study show that all programming languages can be appropriately deployed with an average time of 60 seconds
19
Muhammad, Owais Khan, Khan Jumani Awais, Farhan, Ahmed Siddique Waqas, and Ali Shaikh Asad. "Fast Delivery, Continuously Build, Testing and Deployment with DevOps Pipeline Techniques on Cloud." Indian Journal of Science and Technology 13, no. 5 (2020): 552–75. https://doi.org/10.17485/ijst/2020/v13i05/148983.
Full textAbstract:
Abstract <strong>Objectives:</strong> To implement the DevOps pipeline on cloud for an organization. That is designed and implemented according to the project requirements. <strong>Methods/findings:</strong> The results of the study are to automate everything using DevOps pipeline on cloud native with executed Continuous Integration (CI), Continuous Delivery (CD), and Monitoring required for the case project. The best practices of DevOps are for automated test execution, automated deployment on different environments, and monitoring of the application. It also maintains the application source code repository structure. <strong>Keywords:</strong> DevOps Pipeline, Culture and Infrastructure Challenges, CI (Continues Integration), CD (Continuous Delivery) Implementation on Cloud
20
Divya Kodi. "Efficient CI/CD Strategies: Integrating Git with automated testing and deployment." World Journal of Advanced Research and Reviews 20, no. 2 (2023): 1517–30. https://doi.org/10.30574/wjarr.2023.20.2.2363.
Full textAbstract:
Continuous Integration( CI) and Continuous Deployment (CD) allow prompt delivery of quality software with lesser disruption between development teams. With this simple yet effective Process, Git is a superb tool; the utility combination of Git with some YAML CI/CD templates makes us a better CI/CD pipeline. Keywords: Continuous integration and delivery, Continuous integration and delivery with Git, Automated testing and deployment, Lean continuous integration and delivery, Agile software development 1. Introduction Continuous Integration (CI) and Continuous Delivery (CD) are two of the most vital methodologies in today's software development environment, as they aid developers in developing, testing, and releasing software in much shorter cycles. This study examines an overview of lean CI/CD with Git - automated testing and deployment methods and techniques and gives an extensive overview of approaches and methods providing tools for lean CI/CD sessions. When Git is embedded in CI/CD workflows, code can seamlessly be transferred between development, test, and production environments to give immediate feedback and reduce downtime. These tools simplify the automatic merging of code, running of tests and deployment, thereby reducing human mistakes, increasing productivity, and speeding up a the process of delivering a higher quality software. CI/CD Tools (Jenkins, GitHub Actions, GitLab CI, etc) are there to automate these processes and help out with the scale. CI/CD involves automated testing to make sure you have sufficient quality and reliability in your software. These tests include unit tests, integration tests, and end-to-end tests, which help developers spot and address issues earlier and prevent defects from escaping from one level of system development to another, making this process less resource-intensive. Moreover, deployment automation (e.g., Docker and Kubernetes) allows organizations to deliver continuously without having to depend too much on people. Then, blue-green and canary deployments allow for updates with zero downtime. It further delves into the economic and operational impacts of adopting CI/CD pipelines. Hence, time-to-market is reduced, resources are utilized better, and teams collaborate well, etc. Thus, resorts to containerization and orchestration technologies render deployments cars scalable and reliable, even in complex ecosystems. Configuration drift, manual errors, etc, are some of the bottlenecks for maintaining large-scale environments and Infrastructure as Code ( IaC ) tools ( Terraform, AWS CloudFormation, etc.) allow for consistent and repeatable processes for deployment. Companies who have adopted CI/CD strategies share how it changed their processes via case studies. By integrating Docker-based deployments with GitLab CI/CD, an e-commerce company was able to increase their deployment speed by as much as 40%, while trunk-based development paired with Jenkins allowed a financial services company to increase their test coverage and speed up releases. These are just some of the many very real benefits of incorporating Git, automated testing, and deployment strategies into a CI/CD process. While they are useful, providing CI/CD pipelines can be complicated. The challenges of scaling pipelines to large repositories, securing secrets and toolchain compatibility are non-trivial. In this paper, we will point out these challenges and suggest steps to overcome them. To help organizations get the most out of CI/CD in their workflows, best practices such as enforcing consistent branching policies in CI/CD tools, integrating quality gates (like SonarQube), and using comprehensive monitoring and logging systems are also covered. Looking forward, new trends, including AI-based CI/CD, serverless pipelines and GitOps, will transform the software delivery landscape. The AI-powered predictive analytics will be used to call relevant offerings from the productivity pipeline, and the serverless architectures will reduce the infrastructure load to run the machine-learned tasks. Taking this a step further is GitOps, a newer paradigm centred around declarative infrastructure management, which can help simplify complex deployments.
21
Azeezat, Raheem, Mercy Osilaja Adeola, Kolawole Ikeoluwa, and Eyo Essien Victor. "Exploring continuous integration and deployment strategies for streamlined DevOps processes in software engineering practices." World Journal of Advanced Research and Reviews 24, no. 3 (2024): 2813–30. https://doi.org/10.5281/zenodo.15241805.
Full textAbstract:
Continuous Integration (CI) and Continuous Deployment (CD) have become fundamental practices in modern software engineering, driving efficiency and reliability in DevOps processes. These strategies emphasize automation, collaboration, and iterative delivery to streamline the development lifecycle, ensuring that software updates are delivered rapidly and consistently. This paper explores advanced CI/CD strategies to optimize DevOps workflows, reduce deployment risks, and enhance the agility of software engineering teams. The study begins with an overview of CI/CD principles, highlighting their role in automating testing, integration, and deployment. It examines common challenges in implementing CI/CD pipelines, including managing dependencies, ensuring test reliability, and handling rollback scenarios. By analysing industry case studies, the research showcases successful implementations of CI/CD pipelines in diverse sectors, detailing the tools, frameworks, and practices that contributed to their success. Key innovations, such as containerization with Docker, orchestration using Kubernetes, and the integration of artificial intelligence for predictive analytics, are discussed as enablers of advanced CI/CD processes. The paper also addresses organizational challenges, such as aligning cross-functional teams and fostering a DevOps culture that prioritizes collaboration and continuous improvement. To ensure long-term success, the study emphasizes the importance of metrics and monitoring in CI/CD pipelines, such as deployment frequency, mean time to recovery, and change failure rate. The paper concludes by presenting a roadmap for evolving CI/CD strategies to meet the demands of increasingly complex software systems and rapid technological advancements. This research offers actionable insights for DevOps practitioners and software engineers aiming to streamline development and delivery processes, fostering innovation and resilience in competitive development environments.
22
Krishna, Mohan Pitchikala. "Enhancing Software Development with CI/CD: Best Practices and Strategies." Journal of Scientific and Engineering Research 9, no. 12 (2022): 172–76. https://doi.org/10.5281/zenodo.13338112.
Full textAbstract:
In the current fast-paced and ever-changing business environment, it is important to be able to quickly adjust to market shifts and customer needs. Agile methodology, which was introduced in 2001 [1], is a powerful methodology that transforms how software development and project management are carried out to meet these demands. Agile methodology embraces Continuous Integration and Continuous Deployment/Delivery (CI/CD) as its integral parts. These two practices are built on four core principles: deliver frequently, get continuous feedback, collaborate more, and be adaptable. The CI practice was initiated in the late 1990s but gained popularity around 2001 when agile methodologies started rising [2]. While they initially boosted productivity, these methods did not change the operations processes sufficiently enough to support faster builds and releases. The situation remained unchanged until 2007 when release automation wasn't common yet; even Continuous Deployment (CD) had no formal name at that time [3]. Developers, testers, and operations were productive but lacked processes for quicker releases. CD grew out of CI during the 2000s before becoming mainstream alongside DevOps practices in the 2010s [4]. Although similar in some aspects CI & CD have different goals: frequent code changes merging with every alteration being thoroughly tested through automation is what Continuous Integration focuses on while Continuous Deployment ensures readiness for deployment into production at any given moment. Together these two practices enable a more flexible, reactive and dependable development process overall. Over a decade has passed since its inception; nevertheless, many companies still fail to fully adopt CI/CD. This white paper explores the impact of CI/CD on software development life cycle (SDLC), provides best practices as well as strategies for streamlining development workflows when implementing full-fledged CI/CD
23
Muppa, Naveen. "Informatica Intellegent Cloud Services Code Deployment with Azure DevOps." Journal of Artificial Intelligence & Cloud Computing 1, no. 4 (2022): 1–3. http://dx.doi.org/10.47363/jaicc/2022(1)278.
Full textAbstract:
Continuous Integration/Continuous Delivery (CI/CD) has become a cornerstone of modern software development, enabling teams to deliver high-quality applications at speed and scale. Informatica Intelligent Cloud Services (IICS) provides a robust platform for data integration and management in the cloud. This abstract explores the implementation of CI/CD practices within IICS, focusing on streamlining the development, testing, and deployment of data integration.
24
Shanmukhi, Bhaskara Sahithi. "Implementing and Using CI/CD: Addressing Key Challenges Faced by Software Developers." INTERANTIONAL JOURNAL OF SCIENTIFIC RESEARCH IN ENGINEERING AND MANAGEMENT 08, no. 008 (2024): 1–3. http://dx.doi.org/10.55041/ijsrem37128.
Full textAbstract:
Software development teams that want to increase the calibre, dependability, and velocity of their software releases must implement continuous integration and delivery (CI/CD) techniques. Developers must now overcome several obstacles as a result of this shift, including the necessity to automate testing and deployment procedures, uphold strict version control, and promote cooperation between the development, testing, and operations teams. This article looks at the main obstacles that developers face when implementing and using CI/CD, and it does so by analysing case studies and current industry research to shed light on real-world obstacles and possible solutions. Keywords Continuous Integration (CI), Continuous Delivery (CD), Automation, Version Control, Security Challenges, Test Automation, Scalability, Integration Complexity, Tool Compatibility, System Design, Resource Management, Skill Gaps, Workflow Vulnerabilities.
25
Vivek, Jain. "Continuous Testing in CI/CD Pipelines." INTERNATIONAL JOURNAL OF INNOVATIVE RESEARCH AND CREATIVE TECHNOLOGY 9, no. 1 (2023): 1–7. https://doi.org/10.5281/zenodo.14883221.
Full textAbstract:
The rapid evolution of software development methodologies has placed increasing emphasis on the need for efficiency, reliability, and speed in delivering high-quality applications. Continuous Integration and Continuous Deployment (CI/CD) have become fundamental in modern DevOps practices, enabling seamless and frequent software releases. At the heart of this automation-driven approach lies Continuous Testing (CT), a critical process that ensures software quality by verifying each code change before deployment. Unlike traditional testing methods that occur later in the development lifecycle, Continuous Testing integrates automated testing throughout the pipeline, reducing defects, mitigating risks, and maintaining stability across different environments. This paper delves into the essential role of Continuous Testing in CI/CD pipelines, outlining its benefits, challenges, and practical solutions. We examine real-world case studies, industry best practices, and emerging trends, such as AI-driven test automation, self-healing tests, and blockchain-based security validation. Additionally, we explore the importance of test environment consistency, performance optimization, and shift-left/shift-right testing approaches. Through this discussion, we aim to provide a comprehensive understanding of Continuous Testing’s transformative impact on software delivery and its promising future directions.
26
Kusumadewi, Rismanda, and Ronald Adrian. "Performance Analysis of Devops Practice Implementation Of CI/CD Using Jenkins." MATICS: Jurnal Ilmu Komputer dan Teknologi Informasi (Journal of Computer Science and Information Technology) 15, no. 2 (2023): 90–95. http://dx.doi.org/10.18860/mat.v15i2.17091.
Full textAbstract:
Continuous Integration and Continuous Delivery (CI/CD) are methods used in agile development to automate and speed up the process of building, testing, and validating services. To support and simplify all development and deployment processes, several methods such as containerized and CI/CD automation are needed. In this research, a DevOps Practice is carried out which includes process integration, deployment, and testing automatically using a tool called Jenkins. These tools are open source automation servers to help the Continuous Integration and Continuous Deployment process. Jenkins is equipped with various open source plugins that can be used to simplify and assist CI/CD automation and testing processes. The implementation of CI/CD in performance testing makes the testing process integrated, automated, and can be run on a regular basis.
27
Ponaka, Kamalakar Reddy. "Systematic Approach to Prevent Code Vulnerabilities using CI/CD Pipelines." INTERANTIONAL JOURNAL OF SCIENTIFIC RESEARCH IN ENGINEERING AND MANAGEMENT 08, no. 11 (2024): 1–6. http://dx.doi.org/10.55041/ijsrem7171.
Full textAbstract:
This paper discusses a systematic approach to integrating Static Application Security Testing (SAST), Software Composition Analysis (SCA), Code Coverage, and Code Quality Checks into Continuous Integration/Continuous Delivery (CI/CD) pipelines. Modern CI/CD pipelines accelerate software delivery but introduce significant security and quality challenges. By incorporating SAST and SCA for security testing, along with code coverage and quality checks, organizations can prevent code vulnerabilities and ensure the maintainability and reliability of their applications. This approach helps development teams shift security and quality controls left, catching issues early in the development lifecycle. Keywords — CI/CD, DevSecOps, Static Application Security Testing (SAST), Software Composition Analysis (SCA), Code Coverage, Code Quality, Vulnerability
28
Dey, Arnab. "Automation for CI/CD Pipeline for Code Delivery with Multiple Technologies." Journal of Mathematical & Computer Applications 1, no. 3 (2022): 1–3. http://dx.doi.org/10.47363/jmca/2022(1)138.
Full textAbstract:
In contemporary software development, the use of diverse technologies is prevalent, introducing challenges in managing Continuous Integration and Continuous Delivery (CI/CD) pipelines. This white paper investigates the complexities associated with deploying code written in multiple technologies within a unified CI/CD pipeline. It proposes a comprehensive solution for effective automation to enhance agility, efficiency, and reliability in software delivery.
29
Suprit Pattanayak, Pranav Murthy, and Aditya Mehra. "Integrating AI into DevOps pipelines: Continuous integration, continuous delivery, and automation in infrastructural management: Projections for future." International Journal of Science and Research Archive 13, no. 1 (2024): 2244–56. http://dx.doi.org/10.30574/ijsra.2024.13.1.1838.
Full textAbstract:
This paper explores the transformative role of Artificial Intelligence (AI) in enhancing DevOps pipelines, focusing on Continuous Integration (CI), Continuous Delivery (CD), and automation in infrastructural management. As organizations increasingly adopt DevOps methodologies to streamline software development and delivery processes, the integration of AI technologies offers significant potential for improving efficiency, quality, and responsiveness. This study reviews current practices in CI/CD and examines how AI-driven tools can automate repetitive tasks, optimize resource allocation, and facilitate predictive analytics for proactive decision-making. Additionally, the paper discusses the challenges and considerations associated with AI integration in DevOps, including cultural shifts, data governance, and the need for skilled personnel. Projections for future developments highlight the potential for AI to create smarter, more adaptive DevOps environments that align with evolving industry demands. By identifying key trends and innovations, this research provides a comprehensive overview of the future landscape of DevOps, positioning AI as a critical enabler of agility and performance.
30
Tarun, Parmar. "Implementing CI/CD in Data Engineering: Streamlining Data Pipelines for Reliable and Scalable Solutions." International Journal of Innovative Research in Engineering & Multidisciplinary Physical Sciences 13, no. 1 (2025): 1–8. https://doi.org/10.5281/zenodo.14762684.
Full textAbstract:
Continuous Integration and Continuous Delivery (CI/CD) have become crucial practices in modern data engineering, streamlining the development and deployment of data pipelines. This study explores the implementation of CI/CD principles in data engineering, highlighting its benefits, methodologies, best practices, challenges, and future directions. By automating the building, testing, and deployment processes, the CI/CD ensures reliability, consistency, and efficiency in data pipeline development. The key steps in implementing CI/CD for data pipelines include version control, modular pipeline design, automated testing, continuous integration, artifact management, infrastructure such as code, and continuous delivery and deployment. Successful implementation requires careful planning, robust version-control systems, comprehensive automated testing, infrastructure-as-code practices, and effective monitoring and logging strategies. Challenges such as ensuring data quality, managing dependencies, and maintaining security and compliance were addressed. The paper also discusses emerging trends, including the adoption of serverless architectures, containerization, and integration of DataOps practices. The potential impact of AI and machine learning on CI/CD practices in data engineering was explored, highlighting areas for future research and development. This paper concludes by emphasizing the importance of CI/CD in building reliable, scalable, and efficient data pipelines, driving innovation, and productivity in modern data engineering practices.
31
Praveen, Kumar Koppanati. "Building Custom CI/CD Pipelines for Java Applications in GitLab." Journal of Scientific and Engineering Research 6, no. 6 (2019): 233–38. https://doi.org/10.5281/zenodo.14005865.
Full textAbstract:
For modern software development, especially for Java applications Continuous Integration and Continuous Deployment (CI/CD) pipelines is a vital aspect. This paper aims to provide an in-depth exploration of building custom CI/CD pipelines in GitLab specifically for Java applications. In this guide, we are going to touch upon proper ways on how you should integrate GitLab CI/CD with Java development tools and strategies for pipeline optimization towards effective testing, as well as deployment; analyze Docker methodology where environment consistency is a concern. This will emphasize the key areas to be considered for security, performance and scalability. The analysis also covers automation techniques for testing and deployment, ensuring high code quality and fast iteration cycles. Developers can therefore use GitLab CI/CD and Java tools in tandem to simplify their workflow, with a consistent stream of production-ready software delivered efficiently.
32
Rapolu, Upesh Kumar. "Leveraging Azure DevOps for Streamlined CI/CD Processes in Application Development." INTERANTIONAL JOURNAL OF SCIENTIFIC RESEARCH IN ENGINEERING AND MANAGEMENT 09, no. 02 (2025): 1–7. https://doi.org/10.55041/ijsrem12417.
Full textAbstract:
Continuous Deployment (CD) and Continuous Integration (CI) are essential in today's rapid software development environment for providing high-quality software quickly. Azure DevOps, a comprehensive suite of tools by Microsoft, significantly enhances CI/CD processes. This paper examines how Azure DevOps optimizes efficiency in software development teams through automation, collaboration, and project management. It details the platform's core services, such as Azure Pipelines, Azure Repos, Azure Test Plans, Azure Artifacts, and Azure Boards, highlighting their impact on streamlining workflows. By adopting Azure DevOps, organizations can achieve faster delivery cycles, maintain high-quality standards, and improve overall productivity. This study aims to provide a thorough understanding of Azure DevOps' transformative potential in modern application development. Keywords—Continuous Integration, Continuous Deployment, Azure DevOps, Software Development, Automation, CI/CD Pipelines
33
Schubert, Anja, and Robert Argent. "Promoting scientific software quality through transition to continuous integration and continuous delivery." Socio-Environmental Systems Modelling 6 (December 3, 2024): 18779. https://doi.org/10.18174/sesmo.18779.
Full textAbstract:
Software quality has been an issue for decades in many areas of scientific modelling for environment applications. Much of the software that has been developed is well-suited to supporting research investigation and application in one-off curated application environments, such as delivering solutions through community-based participatory approaches. However, when releasing the software into constrained production environments, with everyday operational challenges such as missing data, unintended user inputs, variable data quality, and values outside the bounds of those previously tested, lacks in software quality can become apparent. The lacks can result in lost time and effort to get the model running again, loss of trust in the model by users and, potentially, cessation in model use, and early and unexpected end-of-life. There have been many efforts through the years to encourage improved software quality, through approaches such as test-driven development, paired programming, more rigorous documentation, and better and broader user acceptance testing. The basis of many of these approaches is the art and science of software testing, through the whole development chain from unit testing, regression testing, integration testing, functional testing and to user testing. Continuous Integration/ Continuous Development (CI/CD)/ Continuous Deployment uses an automated or semi-automated process pipeline that promotes or progresses software through various stages of 'readiness' in different system realms, from development to testing to production. Faithful application of CI/CD promotes good quality software by requiring the software to pass a series of pre-determined tests before it is accepted into the next realm. Models must meet quality levels and pass automated tests to be able to be promoted. Additionally, governance gateways are used to check non-automated workflow components, such as manual testing. This paper explores the challenges and lessons learned in adoption and application of secure CI/CD in an operational environmental modelling enterprise, and suggests a minimum viable good practice approach for application to scientific environmental modelling.
34
Sinde, Sai Priya, Bhavika Thakkalapally, Meghamala Ramidi, and Sowmya Veeramalla. "Continuous Integration and Deployment Automation in AWS Cloud Infrastructure." International Journal for Research in Applied Science and Engineering Technology 10, no. 6 (2022): 1305–9. http://dx.doi.org/10.22214/ijraset.2022.44106.
Full textAbstract:
Abstract-The primary objective of this project is to figure out how an application is automatically deployed. To automate the deployment, we'll require a container orchestration platform. Kubernetes is now a widely used container orchestration tool. Users can deploy, scale, and manage containerized applications thanks to Kubernetes' robustness. Continuous Integration and Continuous Delivery (CI/CD) of a project is required in modern development, and the focus is on developing and executing tests on every commit to ensure your test environment is constantly up-to-date. From the integration and testing phases through the delivery and deployment phases, CI/CD brings automation and continuous monitoring of programmers throughout their lifecycle. GitHub Actions is one of the CI/CD technology available in the market. By using GitHub as a source code management tool, it's best to use GitHub Actions as a continuous integration and delivery solution because it's supplied by GitHub. This does not require any setting or setup. As a result, incorporating these tools will speed up the deployment of an application. Keywords- GitHub Actions, Amazon Web Services, Continuous Integration and Continuous Deployment, Kubernetes, Workflows.
35
Narendar, Kumar Ale. "Integrating Performance Testing into CI/CD Pipelines for Test Automation." Journal of Scientific and Engineering Research 7, no. 6 (2020): 272–78. https://doi.org/10.5281/zenodo.12754783.
Full textAbstract:
Integrating performance testing into Continuous Integration and Continuous Deployment (CI/CD) pipelines is essential for ensuring the scalability, reliability, and responsiveness of modern software applications. This paper explores the strategies, tools, and best practices for embedding performance testing into CI/CD workflows, emphasizing the benefits and challenges of this integration within the context of test automation. By incorporating performance tests early and continuously in the development lifecycle, organizations can detect performance issues promptly and deliver high-quality software efficiently.
36
Singh, Avishek. "A Comparison on Continuous Integration and Continuous Deployment (CI/CD) on Cloud Based on Various Deployment and Testing Strategies." International Journal for Research in Applied Science and Engineering Technology 9, no. VI (2021): 4968–77. http://dx.doi.org/10.22214/ijraset.2021.36038.
Full textAbstract:
Continuous Integration/Continuous Delivery/Deployment (CI/CD) emphasizes the rapid release of small, incremental changes and the use of automation throughout the development process. CI/CD technique is central to DevOps and key to its success. Consumers expect to have continuous interaction with DevOps team so that they can provide their continuous feedback. DevOps is blending of two terms: development and operations which aims to provide conjoin approach to industry’s software development and operation team job in software development lifecycle. 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. Shows the comparison on deployments. With the increasing interest in 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.
37
Sachin, R. Doddaguni, R. Rohith, Asif S. Salman, and M. N. Manas. "Understanding SDLC using CI/CD pipeline." International Journal of Soft Computing and Engineering (IJSCE) 9, no. 6 (2020): 22–25. https://doi.org/10.35940/ijsce.F3405.059620.
Full textAbstract:
Development of complex and quality software necessitates the use of a development model, so that the development process is efficient, reliable and faster. Software development life cycle (SDLC) is a well-defined and wellorganized process used to plan, develop, deploy and maintain high quality software systems. DevOps is one recent addition to SDLC that ensures that the development and operations team collaborate to accelerate the deployment and delivery of higher quality software products. This paper throws a light on how development processes are accelerated using DevOps tactics like continuous integration and deployment (CI/CD) pipelines. however, there are several factors that prevent the organizations from using these approaches. Discovering the evolution of DevOps and its continuous practices, gives a thorough understanding of the importance of the DevOps culture. Manual deployment and testing increase the feedback time of a commit operation. The paper discusses various tools available in the DevOps community that can be used to automate various stages of continuous integration and deployment pipeline, so that the feedback time is reduced.
38
S.K, Arpita, Amrathesh Amrathesh, and Dr Govinda Raju M. "A review on Continuous Integration, Delivery and Deployment using Jenkins." Journal of University of Shanghai for Science and Technology 23, no. 06 (2021): 919–22. http://dx.doi.org/10.51201/jusst/21/05376.
Full textAbstract:
Continuous Integration (CI) is the technique of integrating small changes made to the code more often rather than waiting till the end of the development cycle for integration. The software practice wherein the software deployment can be done anytime to the market is called Continuous Delivery (CD). With continuous integration and continuous delivery, the problem of taking time to find and resolve the bug can be reduced to a large extent. As the time to find the bugs and fix them gets reduced, many releases adhering to the given timeline can be made by an organization. Various software tools have been developed for the continuous integration process which includes Jenkins, Bitbucket, TeamCity. In this paper, a review on the standard practices, approaches, challenges faced while using the continuous integration/delivery in the software development, methods of solving them, and using Jenkins for the implantation of continuous integration/delivery is done.
39
Sarathe Krisshnan Jutoo Vijayaraghavan. "Security as code: Transforming DevSecOps through CI/CD Integration." World Journal of Advanced Engineering Technology and Sciences 15, no. 1 (2025): 2219–25. https://doi.org/10.30574/wjaets.2025.15.1.0446.
Full textAbstract:
Security as Code (Sac) represents a transformative approach to addressing the critical challenge of balancing rapid software delivery with robust security measures. By embedding security directly into continuous integration and continuous deployment pipelines, Sac enables organizations to automate, standardize, and scale security practices throughout the software development lifecycle. This integration transforms security from a bottleneck into an enabler of development velocity while significantly enhancing risk posture. The article explores the theoretical framework of Sac, including its foundations in immutability, shift-left principles, and automated feedback mechanisms. Implementation strategies within Jenkins pipelines highlight practical approaches to security scanning integration, policy as code, secrets management, and compliance automation. The organizational impact of Sac implementation extends beyond technical improvements to catalyze cultural transformation, breaking down traditional silos between development, operations, and security teams. Despite compelling benefits, challenges persist in tool integration, skills availability, governance requirements, and cultural resistance. When properly addressed, these obstacles give way to a security model that is more consistent, efficient, and effective than traditional approaches, ultimately enabling organizations to build more resilient systems without Sacrificing delivery speed.
40
Ponaka, Kamalakar Reddy. "Shift-left approach for Vulnerability Management in SDLC." INTERANTIONAL JOURNAL OF SCIENTIFIC RESEARCH IN ENGINEERING AND MANAGEMENT 08, no. 10 (2024): 1–14. http://dx.doi.org/10.55041/ijsrem9417.
Full textAbstract:
Security vulnerabilities in software development can lead to severe risks if not addressed promptly. By adopting a shift-left approach and implementing gating mechanisms in Continuous Integration/Continuous Delivery (CI/CD) pipelines, organizations can mitigate the impact of high and critical vulnerabilities early in the Software Development Life Cycle (SDLC). This paper discusses a practical methodology for integrating security gates into the CI/CD pipeline to prevent the release of software with critical security flaws. Keywords —Vulnerability Management, Shift-Left Security, CI/CD Pipeline, High Vulnerabilities, Critical Vulnerabilities, Security Gating, SDLC, GitLab, Automation.
41
Thatikonda, Vamsi Krishna. "Beyond the Buzz: A Journey Through CI/CD Principles and Best Practices." European Journal of Theoretical and Applied Sciences 1, no. 5 (2023): 334–40. http://dx.doi.org/10.59324/ejtas.2023.1(5).24.
Full textAbstract:
Continuous Integration and Continuous Deployment (CI/CD) are pivotal in modern software development. Shifting from the classic waterfall models, the current age is dominated by Agile methodologies and DevOps practices. This article explores CI and CD's core principles, differences, and similarities. It touches upon essential techniques such as automation, ensuring consistency, and the importance of quick feedback mechanisms. Beyond these, the discussion extends to cutting-edge methods, infrastructure as code, potential security considerations, and monitoring within CI/CD environments. While CI/CD offers numerous benefits, it's essential to acknowledge its challenges, which necessitate attention and action. With an ever-evolving landscape featuring trends like AI/ML integration into CI/CD, businesses find themselves at a juncture where embracing and finetuning CI/CD is vital for competent software delivery.
42
Naveen, Vemuri, Thaneeru Naresh, and Manoj Tatikonda Venkata. "AI-Optimized DevOps for Streamlined Cloud CI/CD." AI-Optimized DevOps for Streamlined Cloud CI/CD 9, no. 2 (2024): 7. https://doi.org/10.5281/zenodo.10673085.
Full textAbstract:
This research pays attention to the merging of Development Operations with Artificial Intelligence (AI). It starts by realizing that AI will be an important factor in many aspects of work and that it will be automating some job functions. Consequently, AI will be presented as a tool that will enhance knowledge acquisition, provide job performance and professional development. The story stresses the opportunity cost attributed to the shift from software licensing to Software as a Service (SaaS) and underscores the benefits gained through early and regular software release by the organizations which have adopted the practice. DevOps, as a revolutionary approach, seeks to eliminate the gaps in the two central processes namely development and operations. The technology emerging, which includes big data, cloud computing, and mobile internet, calls for quick software deployment and consequently, the DevOps approach is what you get. However, DevOps is a unified approach. In the abstract, it will talk about continuous integration (CI) and continuous delivery (CD) spotting the cost-effectiveness and role of automation in the production process. Through AI and DevOps described, air is evident which is the AI role in automation and troubleshooting development in the software and hardware field. In the paragraph the author puts forth AI-optimized DevOps as a proposal that is not only efficient in development and distribution process but also fast in pacing. The overall wrap-up summarizes the AIOps and MLOps applications in conjunction with DevOps workflow to eliminate disconnection between machine learning model development and operational deployment. The big picture actually is condensed at the end. It outlines exactly how the AI DevOps approach works in modern software development, with particular focus on the cloud CI/ CD platform. Keywords:- AI-Optimized DevOps, Continuous Integration, Continuous Delivery, Automation in Software Deployment, Streamlined Cloud CI/CD, AIOps and MLOps Integration
43
Kamalakar, Reddy Ponaka. "A Scalable and Secure CI/CD Platform: High Availability and Disaster Recovery Approach." INTERNATIONAL JOURNAL OF INNOVATIVE RESEARCH AND CREATIVE TECHNOLOGY 6, no. 3 (2020): 1–5. https://doi.org/10.5281/zenodo.14045480.
Full textAbstract:
This paper presents a scalable and secure continuous integration/continuous deployment (CI/CD) platform architecture for on-premise deployments. It highlights key features for implementing high availability (HA) and disaster recovery (DR) strategies, addressing scalability, security, and resilience. With the increasing reliance on CI/CD pipelines for rapid software delivery, ensuring that these platforms remain operational under adverse conditions, such as hardware failures or data center outages, is critical. This paper provides methodologies and best practices for achieving HA and DR in large-scale CI/CD environments.
44
Azeezat Raheem, Adeola Mercy Osilaja, Ikeoluwa Kolawole, and Victor Eyo Essien. "Exploring continuous integration and deployment strategies for streamlined DevOps processes in software engineering practices." World Journal of Advanced Research and Reviews 24, no. 3 (2024): 2813–30. https://doi.org/10.30574/wjarr.2024.24.3.3988.
Full textAbstract:
Continuous Integration (CI) and Continuous Deployment (CD) have become fundamental practices in modern software engineering, driving efficiency and reliability in DevOps processes. These strategies emphasize automation, collaboration, and iterative delivery to streamline the development lifecycle, ensuring that software updates are delivered rapidly and consistently. This paper explores advanced CI/CD strategies to optimize DevOps workflows, reduce deployment risks, and enhance the agility of software engineering teams. The study begins with an overview of CI/CD principles, highlighting their role in automating testing, integration, and deployment. It examines common challenges in implementing CI/CD pipelines, including managing dependencies, ensuring test reliability, and handling rollback scenarios. By analysing industry case studies, the research showcases successful implementations of CI/CD pipelines in diverse sectors, detailing the tools, frameworks, and practices that contributed to their success. Key innovations, such as containerization with Docker, orchestration using Kubernetes, and the integration of artificial intelligence for predictive analytics, are discussed as enablers of advanced CI/CD processes. The paper also addresses organizational challenges, such as aligning cross-functional teams and fostering a DevOps culture that prioritizes collaboration and continuous improvement. To ensure long-term success, the study emphasizes the importance of metrics and monitoring in CI/CD pipelines, such as deployment frequency, mean time to recovery, and change failure rate. The paper concludes by presenting a roadmap for evolving CI/CD strategies to meet the demands of increasingly complex software systems and rapid technological advancements. This research offers actionable insights for DevOps practitioners and software engineers aiming to streamline development and delivery processes, fostering innovation and resilience in competitive development environments.
45
Emmanuel Akpe, Oyinomomo-emi, Denis Kisina, Oluwasanmi Segun Adanigbo, Abel Chukwuemeke Uzoka, and Nneka Adaobi Ochuba. "A Conceptual Framework for Building Cost-Conscious CI/CD Workflows in Agile Software Teams 2583-6641." International Journal of Management and Organizational Research 2, no. 2 (2023): 135–42. https://doi.org/10.54660/ijmor.2023.2.2.135-142.
Full textAbstract:
This paper presents a conceptual framework for building cost-conscious Continuous Integration/Continuous Deployment (CI/CD) workflows within Agile software teams. With the rapid adoption of Agile methodologies and the increasing reliance on CI/CD pipelines, managing the cost of software delivery has become a critical challenge. The proposed framework addresses the growing need for cost optimization by focusing on the integration of automation, resource management, and the selection of appropriate tools, while maintaining high performance and quality in software development. Key components of the framework include defining cost-conscious CI/CD, optimizing pipeline architecture, and establishing best practices for implementation. The paper also explores the common challenges in cost management, such as tool selection and infrastructure scaling, and offers strategies for overcoming these challenges through automation and optimization. Real-world case studies illustrate the successful application of cost-conscious CI/CD workflows in Agile teams. The findings emphasize the importance of continuous monitoring and iterative adjustments to achieve sustainable, cost-efficient software delivery. The paper concludes with implications for Agile teams, highlighting the long-term benefits of adopting cost-conscious approaches, and suggests areas for future research and development in CI/CD cost management.
46
Widiantara, I. Wayan, I. Nyoman Suweta Nugraha, and Luh Putu Risma Noviana. "RANCANG BANGUN SISTEM CONTINUOUS INTEGRATION (CI) DAN CONTINUOUS DELIVERY (CD) MENGGUNAKAN JENKINS PADA APLIKASI BERBASIS WEB." Jurnal Manajemen dan Teknologi Informasi 14, no. 1 (2024): 37–40. http://dx.doi.org/10.59819/jmti.v14i1.3678.
Full textAbstract:
Perkembangan teknologi yang semakin maju mengakibatkan perkembangan aplikasi yang juga semakin maju dimana kebutuhan akan perangkat lunak aplikasi semakin meningkat, sebuah perusahaan teknologi selalu mengembangkan dan memperbaharui aplikasi yang telah mereka kembangkan. Proses pengembangan membutuhkan waktu yang lebih lama karena prosesnya yang rumit terutama dalam proses build dan deployment agar perangkat lunak aplikasi tersebut dapat dinikmati oleh orang-orang di seluruh dunia melalui internet. Untuk mengatasi masalah tersebut, penelitian ini membantu untuk membangun dan mengembangkan sistem yang dapat mengotomatisasi semua proses build dan deployment sehingga proses tersebut tidak dilakukan dengan campur tangan manusia yang dapat mengakibatkan terjadinya human error dan juga downtime sehingga aplikasi yang sedang di-deploy tidak dapat diakses karena kesalahan tersebut, metode RAD atau Rapid Application Development digunakan untuk mengembangkan sistem ini dengan tujuan agar proses pengembangan menjadi lebih mudah dan lebih cepat. DevOps Engineer membantu dalam proses implementasi Continuous Integration yang diharapkan dapat mempersingkat waktu keseluruhan SDLC (Software Development Life Cycle) dengan menggunakan tool open source bernama Jenkins, sehingga proses pengembangan aplikasi dapat berjalan dengan cepat dan tepat waktu sesuai dengan waktu yang telah ditentukan agar semua pengguna dapat menikmati internet
47
Neelapu, Mohnish. "Enhancing Quality Assurance Efficiency through CI/CD Integration: A Case Study on Automated Testing and Deployment." International Scientific Journal of Engineering and Management 03, no. 06 (2024): 1–8. https://doi.org/10.55041/isjem02016.
Full textAbstract:
Continuous Integration and Continuous Deployment (CI/CD) have transformed software quality assurance (QA) radically by test automation and reducing release cycles. This research measures the effect of CI/CD integration into current QA processes in a real-world software development context based on a case study. The study presents comparisons on main metrics like rate of deployment, rate of detected defects, mean time to restore (MTTR), and ratio of automating efficiently with comparison to legacy QA vs. CI/CD-based processes. Qualitative data from interviews, survey data, log data, and CI/CD pipeline metrics have been used to determine the software quality and delivery speed impact. Results show that CI/CD improves testing efficiency by a large margin, lowering test execution time from 6 hours to 1.5 hours and defect detection from 70% to 92%. Although CI/CD has drawbacks such as infrastructure cost and flaky tests, practices like test environment stabilization and resource efficiency countered these drawbacks. The study recognizes CI/CD's role in improving agility, collaboration, and reliability in software development as a major method for modern QA practices. Keywords- Software Quality Assurance, Agile Development, Deployment Efficiency, Continuous Integration and Automated Testing.
48
Pant, Deepak. "EduDevOps : The Ultimate CI/CD Corporate Devops Pipeline Project." INTERNATIONAL JOURNAL OF SCIENTIFIC RESEARCH IN ENGINEERING AND MANAGEMENT 09, no. 05 (2025): 1–9. https://doi.org/10.55041/ijsrem47302.
Full textAbstract:
Abstract -The accelerated pace of digital transformation has heightened the requirement for efficient, scalable, and reliable software delivery practices. Legacy software development and deployment pipelines are typically inefficient owing to manual interventions, siloed teams, and constraints in scalability. This research presents a comprehensive DevOps Capstone Project that takes aim at conceptualizing and executing an enterprise-scale Continuous Integration and Continuous Deployment (CI/CD) pipeline. By utilizing Docker, Kubernetes, Terraform, and other automated tools, the project addresses significant software delivery concerns such as speed, quality, and operational efficiency. The findings demonstrate how a consolidated DevOps pipeline can enable agile development, reduce time-to-market, and improve overall software quality, thereby positioning organizations for long-term digital success Key Words: DevOps, CI/CD Pipeline, Automation, Containerization, Infrastructure as Code
49
Researcher. "SECURING CI/CD PIPELINES: STRATEGIES FOR MITIGATING RISKS IN MODERN SOFTWARE DELIVERY." International Journal of Engineering and Technology Research (IJETR) 9, no. 2 (2024): 1–9. https://doi.org/10.5281/zenodo.13365012.
Full textAbstract:
This comprehensive article explores the critical challenge of securing Continuous Integration and Continuous Deployment (CI/CD) pipelines in modern software development. It addresses the common security threats faced by organizations, including credential leaks, supply chain attacks, and unauthorized access, while offering actionable strategies to mitigate these risks. The paper delves into best practices for enhancing CI/CD security, covering crucial aspects such as secret management, encryption techniques, secure CI/CD tools, immutable infrastructure, and comprehensive security testing methodologies. Additionally, it emphasizes the importance of role-based access control and continuous learning in maintaining robust security postures. Through an examination of real-world case studies, the article provides insights into successful implementations of secure CI/CD pipelines and valuable lessons learned from security breaches. Looking towards the future, the paper discusses emerging trends in CI/CD security, including the potential of artificial intelligence and machine learning in enhancing threat detection, as well as the growing adoption of shift-left security practices. By synthesizing current research, industry best practices, and forward-looking approaches, this article serves as a vital resource for organizations seeking to fortify their software delivery processes against evolving cyber threats while maintaining the agility and efficiency that CI/CD pipelines offer.
50
Berko, Andriy, and Ivan Koblyk. "Information System for Managing the Process of Continuous Software Delivery." Vìsnik Nacìonalʹnogo unìversitetu "Lʹvìvsʹka polìtehnìka". Serìâ Ìnformacìjnì sistemi ta merežì 15 (July 15, 2024): 238–51. http://dx.doi.org/10.23939/sisn2024.15.238.
Full textAbstract:
Today, the direction of DevOps is an essential component in the execution of IT projects of various scales. This determines the need to develop the latest progressive approaches, methods, and technologies to ensure the effective activity of DevOps specialists. One of such popular solutions is continuous integration (CI) and continuous delivery (CD) of software. This approach (CI/CD) makes it possible to significantly speed up the processes of software development, testing, and implementation, improve the quality of development results, and ensure the controllability and manageability of these processes. A key factor in CI/CD processes is the use of tools to automate the work of DevOps specialists. The work describes a system for managing the continuous delivery of software, developed based on the modern application experience of leading companies.