Relevant bibliographies by topics / Continuous Integration/Continuous Delivery (CI/CD)

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers

Academic literature on the topic 'Continuous Integration/Continuous Delivery (CI/CD)'

Author: Grafiati
Published: 7 June 2025
Last updated: 11 July 2025

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources 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.

Journal articles on the topic "Continuous Integration/Continuous Delivery (CI/CD)"

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
APA, Harvard, Vancouver, ISO, and other styles
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 text
Abstract:
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
APA, Harvard, Vancouver, ISO, and other styles
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 text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
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 text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
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 text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
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 text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
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 text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
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 text
Abstract:
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
APA, Harvard, Vancouver, ISO, and other styles
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 text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
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 text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Continuous Integration/Continuous Delivery (CI/CD)"

1

Víšek, Jakub. "Hromadná orchestrácia v multirepo CI/CD prostrediach." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2021. http://www.nusl.cz/ntk/nusl-445562.

Full text
Abstract:
Multirepo model přístupu ke správě a verzování zdrojového kódu, jež zahrnuje použití mnoha oddělených repozitářů verzovacích systémů, je poslední dobou často zmiňován v odborné literatuře. Jednou z jeho nevýhod je množství zdlouhavých, nezajímavých a repetitivních úkonů, které je nutno provádět při hromadných operacích tvořících transakce napříč těmito repozitáři. Multirepo repozitáře navíc umožňují využití široké škály technologií, což jen umocňuje riziko lidské chyby, ke které při ručně prováděných hromadných operacích může dojít. V rámci této práce je navrženo, implementováno a otestováno řešení pro automatizaci operací prováděných napříč množstvím repozitářů uspořádaných v multirepo modelu, což s nimi uživatelům zlepšuje zkušenost.
APA, Harvard, Vancouver, ISO, and other styles
2

Petersson, Karl. "Test automation in a CI/CD workflow." Thesis, Linnéuniversitetet, Institutionen för datavetenskap och medieteknik (DM), 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-96253.

Full text
Abstract:
The procedure of testing the implemented software is important and should be an essential and integrated part of the development process. In order for the testing to be meaningful it is important that the testing procedure ensures that the developed software meet certain requirements. The testing procure is often controlled by some sort of test specification. For many companies it is desirable to automate this procure. The focus of this thesis has been to automate a small subpart of the manual tests today performed related to SAAB:s air traffic management system. The automation has been achieved by studying the existing test specification which involves a lot of manual operations and to write software that mimics a few of these test cases. The thesis has resulted in a test framework which automates a small subset of the manual tests performed today. The framework has been designed to be scalable and to easily allow more test cases to be added by the personnel when time permits. The test framework has also been integrated with SAAB:s existing CI/CD workflow.
APA, Harvard, Vancouver, ISO, and other styles
3

Persson, Simone. "List of Security Concerns within Continuous Software Evolution." Thesis, KTH, Skolan för elektroteknik och datavetenskap (EECS), 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-254881.

Full text
Abstract:
The amount of data being collected is increasing astronomically. Hence questions about privacy and data security are becoming more important than ever. A fast-changing culture is also reflected in the demands and requirements placed on software systems. Products and services need to evolve with the demands and feedback from customers to stay relevant on the market. Working methods and technologies have been refined to afford updating software continuously. However, rapidly changing software cause concern for the quality and level of security in the release. This thesis is a comprehensive literature study, reviewing the challenges of ensuring secure practises for continuously evolving software. The problem solved by the thesis is lack of an overall picture of the security concerns during continuous evolution. The findings are summarised in a checklist of areas of concern for security when maintaining and updating systems with continuous practises in cloud environments. This study shows that ensuring security, while delivering continuous releases, is a daunting task. It requires close collaboration between teams handling different aspects of software. This, in turn, entails a widening of competences to include knowledge about the work of other departments. It is concluded that personnel with this wide range of skill will be hard to acquire.<br>I en tid då mängden data som samlas in om individer ökar i ohindrad takt, blir frågor om integritet och informationssäkerhet viktigare än någonsin. Kraven på snabb utveckling och förändring präglar även metoderna för mjukvaruutveckling. Produkter och tjänster måste konstant anpassas efter kundernas önskemål för att förbli relevant på marknaden. Arbetssätt och teknologier har utvecklats över tid för att möjliggöra mjukvara som uppdateras kontinuerligt. Konstant föränderlig mjukvara leder dock till oro för kvalitén och säkerheten av uppdateringarna. Den här uppsatsen är en litteraturstudie som undersöker utmaningarna att säkerställa säkerhet för mjukvara som uppdateras kontinuerligt. Problemet som löses genom studien är den saknade helhetsbilden av säkerhetsproblem vid kontinuerligt föränderlig mjukvara. Resultatet sammanfattas i en checklista för områden som väcker oro för säkerheten vid arbetssätt som tillåter kontinuerliga uppdateringar i moln-miljöer. Studien visar att leverera säkra lösningar kontinuerligt är en svår uppgift. Det kräver nära samarbete mellan team som sköter olika delar av mjukvaruutveckling. Detta fordrar vida kompetenser som inkluderar förståelse av varandras arbete. Att finna personal med tillräckligt vida kompetenser uppskattas vara problematiskt.
APA, Harvard, Vancouver, ISO, and other styles
4

Wallström, Andreas. "Guidance on Implementing Agile Software Development Methods within a Traditional Environment." Thesis, KTH, Industriell ekonomi och organisation (Inst.), 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-296990.

Full text
Abstract:
Agile software development methods keep increasing in popularity. Many organizations who are using traditional software development methods, such as water-fall and stagegate based methods are switching to agile software development methods. This transition can be challenging, especially for organizations using project governance models that hinder the adoption of agile practices. This study aims to provide guidance to managers on how to introduce agile software development methods in such traditional organizations. The study is a single-case study on a large governmental agency in Sweden. Eight interviews with developers, team-leads and managers were conducted. The study identifies practical tools and ideas that managers can use to introduce a shared definition of agile, adopting an agile mindset, dedicated teams, and CI&amp;CD. Together, this guidance supports managers with the introduction of agile software development methods in organizations utilizing traditional project governance structures and traditional software development methods.<br>Agila systemutvecklingsmetoder fortsätter öka i popularitet. Många organisationer som använder sig av traditionella systemutvecklingsmetoder så som vattenfallsmodellen byter till agila systemutvecklingsmetoder. Denna övergång kan vara utmanande, speciellt för organisationer som använder sig av projektbaserade förvaltningsmodeller som hindrar implementeringen av agila metoder. Den här studien syftar till att ge vägledningen till chefer kring hur de kan introducera agila systemutvecklingsmetoder iden nyss nämnda typen av traditionella organisationer. Studien är en fallstudie gjort på en stor myndighet i Sverige. Åtta intervjuer med systemutvecklare, lag-ledare och chefer har utförts. Studien identifierar verktyg och idéer som chefer kan använda sig avför att introducera en delad gemensam definition av agilt, anamma ett agilt tankesätt, introducera dedikerade teams och CI&amp;CD. Tillsammans hjälper de här verktygen med introduktionen av agila systemutvecklingsmetoder i organisationer som använder sig av traditionella systemutvecklingsmetoder och förvaltningsmodeller.
APA, Harvard, Vancouver, ISO, and other styles
5

Zhygulskyy, Mykyta. "AUTOMATED, SCHEDULED AND CI /CD WEB INJECTION." Master's thesis, 2021. http://hdl.handle.net/10400.8/5786.

Full text
Abstract:
This report is made within the Curricular Unit (UC) Project, in the 2nd year of the Master in Cyber-security and Forensic Informatics (MCIF) provided by the Polytechnic Institute of Leiria (IPL). The purpose of this project is to study SQL Injection vulnerabilities in web applications. According to OWASP (Open Web Application Security Project) [20][19], this is one of the more prevalent attacks on web applications. As part of this work a web application was implemented, which can from a URL address, go through all the endpoints of the target application and test for SQL Injection vulnerabilities. The application also makes allows for scheduling of the tests and it is integrable with Continuous Integration / Continuous Delivery (CI/CD) environments. According to the literature on the subject, there are several algorithms that can be employed to test for existing SQL Injection vulnerabilities in a web application. In this document, we analyze them both from a theoretical and an implementation point of view. In order to better understand the subject, and produce a useful tool in this space. With the development of this project, we concluded that it is possible to integrate SQL vulnerability tests, with CI/CD pipeline and automate the development process of an application, with the execution of SQL injection tests in an automated way.
APA, Harvard, Vancouver, ISO, and other styles
6

Rolo, Simão Pedro Ferreira. "AGILIZAÇÃO DO PROCESSO DE ENTREGA DE SOFTWARE." Master's thesis, 2021. http://hdl.handle.net/10400.8/6267.

Full text
Abstract:
Neste documento descreve-se o estágio curricular desenvolvido no âmbito da Unidade Curricular de Estágio do Mestrado de Engenharia Informática - Computação Móvel, pertencente ao Instituto Politécnico de Leiria, e realizado no Grupo Lusiaves SGPS,SA, no período compreendido entre Outubro de 2019 e Junho de 2020. Durante o período de estágio o objetivo foi de desenvolver mecanismos de Continuous Integration e Continuous Development, assim como o desenho e migração de aplicações monolíticas para containers . Adicionalmente, foi também essencial desenvolver aptidões relativas à Plataforma de Integrações utilizada na Empresa (Boomi), assim como aptidões ao nível de infraestrutura de empresa (AWS). Durante a duração do estágio e com recurso a uma metodologia ágil, foi possível implementar ferramentas, tecnologias e métodos que permitiram concretizar o objetivo inicial de se ter processos de Continuous Integration, Continuous Development e de contentores escaláveis. Foi possível implementar algumas soluções que ajudaram não só na qualidade dos dados de logging, como a solução de contentorização pretendida, assim como mecanismos que simplificaram o Continuous Integration e o Continuous Development.
APA, Harvard, Vancouver, ISO, and other styles

Books on the topic "Continuous Integration/Continuous Delivery (CI/CD)"

1

van Merode, Henry. Continuous Integration (CI) and Continuous Delivery (CD). Apress, 2023. http://dx.doi.org/10.1007/978-1-4842-9228-0.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Continuous Delivery with Docker and Jenkins,: Create Secure Applications by Building Complete CI/CD Pipelines. de Gruyter GmbH, Walter, 2019.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

Rafał Leszko. Continuous Delivery with Docker and Jenkins: Create Secure Applications by Building Complete CI/CD Pipelines. Packt Publishing, Limited, 2022.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
4

Continuous Delivery with Docker and Jenkins, 3rd Edition: Create Secure Applications by Building Complete CI/CD Pipelines. de Gruyter GmbH, Walter, 2022.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

Leszko, Rafal. Continuous Delivery with Docker and Jenkins: Create secure applications by building complete CI/CD pipelines, 2nd Edition. Packt Publishing, 2019.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
6

Belmont, Jean-Marcel. Hands-On Continuous Integration and Delivery: Build and Release Quality Software at Scale with Jenkins, Travis CI, and CircleCI. Packt Publishing, Limited, 2018.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
7

Learning Continuous Integration with Jenkins: An End-To-end Guide to Creating Operational, Secure, Resilient, and Cost-effective CI/CD Processes. de Gruyter GmbH, Walter, 2024.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
8

Learning Continuous Integration with Jenkins: An End-To-end Guide to Creating Operational, Secure, Resilient, and Cost-effective CI/CD Processes. Packt Publishing, Limited, 2024.

Find full text
APA, Harvard, Vancouver, ISO, and other styles

Book chapters on the topic "Continuous Integration/Continuous Delivery (CI/CD)"

1

van Merode, Henry. "CI/CD Concepts." In Continuous Integration (CI) and Continuous Delivery (CD). Apress, 2023. http://dx.doi.org/10.1007/978-1-4842-9228-0_2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

van Merode, Henry. "The Pitfalls of CI/CD." In Continuous Integration (CI) and Continuous Delivery (CD). Apress, 2023. http://dx.doi.org/10.1007/978-1-4842-9228-0_1.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

van Merode, Henry. "Use Case." In Continuous Integration (CI) and Continuous Delivery (CD). Apress, 2023. http://dx.doi.org/10.1007/978-1-4842-9228-0_9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

van Merode, Henry. "Requirements Analysis." In Continuous Integration (CI) and Continuous Delivery (CD). Apress, 2023. http://dx.doi.org/10.1007/978-1-4842-9228-0_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

van Merode, Henry. "Pipeline Implementation." In Continuous Integration (CI) and Continuous Delivery (CD). Apress, 2023. http://dx.doi.org/10.1007/978-1-4842-9228-0_7.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

van Merode, Henry. "Operate and Monitor." In Continuous Integration (CI) and Continuous Delivery (CD). Apress, 2023. http://dx.doi.org/10.1007/978-1-4842-9228-0_8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

van Merode, Henry. "Testing Pipelines." In Continuous Integration (CI) and Continuous Delivery (CD). Apress, 2023. http://dx.doi.org/10.1007/978-1-4842-9228-0_6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

van Merode, Henry. "Pipeline Development." In Continuous Integration (CI) and Continuous Delivery (CD). Apress, 2023. http://dx.doi.org/10.1007/978-1-4842-9228-0_5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

van Merode, Henry. "Pipeline Design." In Continuous Integration (CI) and Continuous Delivery (CD). Apress, 2023. http://dx.doi.org/10.1007/978-1-4842-9228-0_4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Slama, Dirk. "Holistic AIoT DevOps." In The Digital Playbook. Springer International Publishing, 2023. http://dx.doi.org/10.1007/978-3-030-88221-1_24.

Full text
Abstract:
AbstractThe introduction of DevOps — together with Continuous Integration/Continuous Delivery (CI/CD) — has fundamentally changed the way software is developed, integrated, tested, and deployed. DevOps and CI/CD are key enablers of agile development. However, today’s DevOps practices predominantly focus on cloud and enterprise application development. For successful AIoT products, DevOps will need to be extended to include AI and IoT (Fig. 27.1).
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Continuous Integration/Continuous Delivery (CI/CD)"

1

Saleh, Sabbir, Nazim Madhavji, and John Steinbacher. "A Systematic Literature Review on Continuous Integration and Deployment (CI/CD) for Secure Cloud Computing." In 20th International Conference on Web Information Systems and Technologies. SCITEPRESS - Science and Technology Publications, 2024. http://dx.doi.org/10.5220/0013018500003825.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Pratama, Mohammad Rizky, and Dana Sulistiyo Kusumo. "Implementation of Continuous Integration and Continuous Delivery (CI/CD) on Automatic Performance Testing." In 2021 9th International Conference on Information and Communication Technology (ICoICT). IEEE, 2021. http://dx.doi.org/10.1109/icoict52021.2021.9527496.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Micco, John. "Industrial best practices for continuous integration (CI) and continuously delivery (CD) (invited talk)." In ESEC/FSE '21: 29th ACM Joint European Software Engineering Conference and Symposium on the Foundations of Software Engineering. ACM, 2021. http://dx.doi.org/10.1145/3468264.3478693.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Fiterman, Eric, Kenneth Brown, Daniel Mallia, and Justin Tornetta. "Integrating synthetic data validation and quality benchmarks into a continuous integration/continuous delivery (CI/CD) data-generation pipeline." In Anomaly Detection and Imaging with X-Rays (ADIX) IX, edited by Amit Ashok, Michael E. Gehm, and Joel A. Greenberg. SPIE, 2024. http://dx.doi.org/10.1117/12.3014548.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Sharma, Priyanshi, and Mugdha Shailendra Kulkarni. "A study on Unlocking the potential of different AI in Continuous Integration and Continuous Delivery (CI/CD)." In 2024 4th International Conference on Innovative Practices in Technology and Management (ICIPTM). IEEE, 2024. http://dx.doi.org/10.1109/iciptm59628.2024.10563618.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Feijó, Diego N., Carlos D. A. de Almeida, and Lincoln S. Rocha. "Studying the Impact of Continuous Delivery Adoption on Atoms of Confusion Rate in Open-Source Projects." In Workshop de Visualização, Evolução e Manutenção de Software. Sociedade Brasileira de Computação - SBC, 2023. http://dx.doi.org/10.5753/vem.2023.235685.

Full text
Abstract:
Atoms of Confusion (AoC) are indivisible code patterns that may cause confusion for developers when trying to understand them, and that have less confusing equivalent patterns. Previous works suggest it is a good practice to avoid them. While there are studies on AoC relating them to bugs, there is not much about their relationship with the practices of Continuous Integration and Continuous Delivery (CI/CD). Since CI/CD is generally praised as a group of good practices, related to better code being released reliably and faster to clients, there’s a possibility that the presence of CI/CD would also impact the presence of AoC, possibly making them less prevalent since they can be problematic to development processes. To clarify this relationship, we analyzed 10 open-source long-lived Java libraries and 10 open-source Java projects for Android, to see if there was any difference in the AoC rate before and after the implementation of CI/CD. Our results show the AoC rate changed for all projects, but we could not find a statistically relevant relationship between these changes and CI/CD.
APA, Harvard, Vancouver, ISO, and other styles
7

Mowad, Abrar Mohammad, Hamed Fawareh, and Mohammad A. Hassan. "Effect of Using Continuous Integration (CI) and Continuous Delivery (CD) Deployment in DevOps to reduce the Gap between Developer and Operation." In 2022 International Arab Conference on Information Technology (ACIT). IEEE, 2022. http://dx.doi.org/10.1109/acit57182.2022.9994139.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Silva, Edson Campolina, Rodolfo Rodrigues, Johnatan Oliveira, Danilo Boechat, and Cleiton Tavares. "Evaluating Test Quality in GitHub Repositories: A Comparative Analysis of CI/CD Practices Using GitHub Actions." In Workshop de Visualização, Evolução e Manutenção de Software. Sociedade Brasileira de Computação - SBC, 2024. http://dx.doi.org/10.5753/vem.2024.3842.

Full text
Abstract:
Tests are present in different stages of software development and perform an important role throughout the lifecycle of an application. Although, test smells are undesirable, as they characterize poorly designed tests that negatively impact their quality. Therefore, the goal of this study is to investigate the quality of tests in GitHub repositories that implement or do not implement Continuous Integration and Continuous Delivery (CI/CD). To achieve this goal, we conduct a comparative analysis between repositories that use GitHub Actions as CI/CD environments and repositories that do not use CI/CD. To evaluate the quality of the test suite, test smells were detected, and bug issues and the time taken to fix these issues were analyzed. In total, 651 repositories that use GitHub Actions and 289 that do not use CI/CD were analyzed. As a result, 1,648,254 test smells were identified in repositories that use GitHub Actions and 709,680 in repositories that do not. It was found that 86.18% of bug-type issues were closed in repositories that use GitHub Actions, compared to 89.20% in those that do not. Furthermore, the median time for resolving bug-type issues was 156 hours in repositories using GitHub Actions, compared to 178 hours in those without CI/CD. Finally, after statistical tests, it was not possible to state that the use of GitHub Actions in the repositories improves the quality of the tests implemented.
APA, Harvard, Vancouver, ISO, and other styles
9

Oliveira, Stephany Mendes, and Daniel Lucrédio. "Guidelines for Data Engineering Documentation in a DevDocOps Approach." In Simpósio Brasileiro de Componentes, Arquiteturas e Reutilização de Software. Sociedade Brasileira de Computação, 2024. http://dx.doi.org/10.5753/sbcars.2024.3834.

Full text
Abstract:
The software development process has been studied since the beginning of technological evolution. Development practices have evolved, requiring processes capable of supporting intensive work, paving the way for agile methodologies. With the growing need for continuous integration (CI) and continuous deployment/delivery (CD), new data architectures have emerged, allowing for scalable, maintainable, and reusable environments, collectively known as DevOps (Development + Operations). In this context, the DevDocOps approach integrates continuous documentation into the software development lifecycle. However, little has been published regarding the benefits of this approach. To address this, an empirical study was conducted, applying findings from the literature to a real development environment by integrating continuous documentation into the data engineering development lifecycle. Based on feedback from developers and technical lead, the results highlight the importance of technical documentation in an agile development environment and demonstrate how automating this process can improve the quality and efficiency of software deliveries.
APA, Harvard, Vancouver, ISO, and other styles
10

Chen, Tianyi. "Challenges and Opportunities in Integrating LLMs into Continuous Integration/Continuous Deployment (CI/CD) Pipelines." In 2024 5th International Seminar on Artificial Intelligence, Networking and Information Technology (AINIT). IEEE, 2024. http://dx.doi.org/10.1109/ainit61980.2024.10581784.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Continuous Integration/Continuous Delivery (CI/CD)' for particular source types:
Journal articles
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography