CI/CD: Difference between revisions
Adding more content without reference this time |
|||
| Line 7: | Line 7: | ||
{{Reflist}} |
{{Reflist}} |
||
== |
== Further reading == |
||
* [https://www.sdxcentral.com/cloud/cloud-native/definitions/what-is-ci-cd-definition/ What Is CI/CD? — Definition] |
|||
* [https://resources.github.com/ci-cd CI/CD explained] |
* [https://resources.github.com/ci-cd CI/CD explained] |
||
* [https://ieeexplore.ieee.org/abstract/document/9314485 A new metamodel approach of CI/CD applied to Internet of Things Ecosystem] |
* [https://ieeexplore.ieee.org/abstract/document/9314485 A new metamodel approach of CI/CD applied to Internet of Things Ecosystem] |
||
Revision as of 17:11, 27 August 2021
In software engineering, CI/CD or CICD is the combined practices of continuous integration (CI) and either continuous delivery or 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. The process contrasts with traditional methods where all updates were integrated into one large batch before rolling out 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.