CI/CD: Difference between revisions
Content deleted Content added
m Aready in Category:Software development, WP:SUBCAT |
According to the DevOps article: "When referring to CI/CD, the “CD” being referenced is usually continuous delivery, not continuous deployment" |
||
| Line 2: | Line 2: | ||
{{for| corporate communication topics|corporate identity|corporate design}} |
{{for| corporate communication topics|corporate identity|corporate design}} |
||
{{Software development process}} |
{{Software development process}} |
||
In [[software engineering]], '''CI/CD''' or '''CICD''' is the combined practices of [[continuous integration]] (CI) and |
In [[software engineering]], '''CI/CD''' or '''CICD''' is the combined practices of [[continuous integration]] (CI) and (more often) [[continuous delivery]] or (less often) [[continuous deployment]] (CD).<ref>{{Cite news |url=https://www.infoworld.com/article/3271126/what-is-cicd-continuous-integration-and-continuous-delivery-explained.html|title=What is CI/CD? Continuous integration and continuous delivery explained|last=Sacolick|first=Isaac|date=2020-01-17|work=[[InfoWorld]]|access-date=2021-06-01|language=en}}</ref> |
||
CI/CD bridges the gaps between development and operation activities and teams by enforcing automation in building, testing and deployment of applications. CI/CD services compile the incremental code changes made by developers, then link and package them into software deliverables.<ref>{{cite book |first=Sander |last=Rossel |title=Continuous Integration, Delivery, and Deployment |date=October 2017 |publisher= Packt Publishing |isbn=978-1-78728-661-0}}</ref> Automated tests verify the software functionality, and automated deployment services deliver them to end users.<ref>{{cite journal |first=Keheliya |last=Gallaba |title=Improving the Robustness and Efficiency of Continuous Integration and Deployment |journal=2019 IEEE International Conference on Software Maintenance and Evolution (ICSME) |date=2019 |pages=619–623 |doi=10.1109/ICSME.2019.00099}}</ref> The aim is to increase early defect discovery, increase productivity, and provide faster release cycles. The process contrasts with traditional methods where a collection of software updates were integrated into one large batch before deploying the newer version. Modern-day [[DevOps]] practices involve continuous development, continuous testing, continuous integration, continuous deployment and continuous monitoring of software applications throughout its development life cycle. The CI/CD practice, or ''CI/CD pipeline'', forms the backbone of modern day DevOps operations. |
CI/CD bridges the gaps between development and operation activities and teams by enforcing automation in building, testing and deployment of applications. CI/CD services compile the incremental code changes made by developers, then link and package them into software deliverables.<ref>{{cite book |first=Sander |last=Rossel |title=Continuous Integration, Delivery, and Deployment |date=October 2017 |publisher= Packt Publishing |isbn=978-1-78728-661-0}}</ref> Automated tests verify the software functionality, and automated deployment services deliver them to end users.<ref>{{cite journal |first=Keheliya |last=Gallaba |title=Improving the Robustness and Efficiency of Continuous Integration and Deployment |journal=2019 IEEE International Conference on Software Maintenance and Evolution (ICSME) |date=2019 |pages=619–623 |doi=10.1109/ICSME.2019.00099}}</ref> The aim is to increase early defect discovery, increase productivity, and provide faster release cycles. The process contrasts with traditional methods where a collection of software updates were integrated into one large batch before deploying the newer version. Modern-day [[DevOps]] practices involve continuous development, continuous testing, continuous integration, continuous deployment and continuous monitoring of software applications throughout its development life cycle. The CI/CD practice, or ''CI/CD pipeline'', forms the backbone of modern day DevOps operations. |
||
Revision as of 11:22, 20 March 2022
| Part of a series on |
| Software development |
|---|
In software engineering, CI/CD or CICD is the combined practices of continuous integration (CI) and (more often) continuous delivery or (less often) continuous deployment (CD).[1]
CI/CD bridges the gaps between development and operation activities and teams by enforcing automation in building, testing and deployment of applications. CI/CD services compile the incremental code changes made by developers, then link and package them into software deliverables.[2] Automated tests verify the software functionality, and automated deployment services deliver them to end users.[3] The aim is to increase early defect discovery, increase productivity, and provide faster release cycles. The process contrasts with traditional methods where a collection of software updates were integrated into one large batch before deploying the newer version. Modern-day DevOps practices involve continuous development, continuous testing, continuous integration, continuous deployment and continuous monitoring of software applications throughout its development life cycle. The CI/CD practice, or CI/CD pipeline, forms the backbone of modern day DevOps operations.
References
- ^ Sacolick, Isaac (2020-01-17). "What is CI/CD? Continuous integration and continuous delivery explained". InfoWorld. Retrieved 2021-06-01.
- ^ Rossel, Sander (October 2017). Continuous Integration, Delivery, and Deployment. Packt Publishing. ISBN 978-1-78728-661-0.
- ^ Gallaba, Keheliya (2019). "Improving the Robustness and Efficiency of Continuous Integration and Deployment". 2019 IEEE International Conference on Software Maintenance and Evolution (ICSME): 619–623. doi:10.1109/ICSME.2019.00099.
External Links
- El Khalyly, B.; Belangour, A.; Banane, M.; Erraissi, A. (2020). "A new metamodel approach of CI/CD applied to Internet of Things Ecosystem". 2020 IEEE 2nd International Conference on Electronics, Control, Optimization and Computer Science (ICECOCS): 1–6. doi:10.1109/ICECOCS50124.2020.9314485.
- Sane, P. (2021). "A Brief Survey of Current Software Engineering Practices in Continuous Integration and Automated Accessibility Testing". 2021 Sixth International Conference on Wireless Communications, Signal Processing and Networking (WiSPNET): 130–134. doi:10.1109/WiSPNET51692.2021.9419464.