CI/CD: Difference between revisions
Tag: Reverted |
Adding more content without reference this time |
||
| Line 3: | Line 3: | ||
In [[software engineering]], '''CI/CD''' or '''CICD''' is the combined practices of [[continuous integration]] (CI) and either [[continuous delivery]] or [[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> |
In [[software engineering]], '''CI/CD''' or '''CICD''' is the combined practices of [[continuous integration]] (CI) and either [[continuous delivery]] or [[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. 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. 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== |
==References== |
||
{{Reflist}} |
{{Reflist}} |
||
Revision as of 17:10, 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.