CI/CD: Difference between revisions
Content deleted Content added
m Removed outdated resources and updated with current news citation Tag: references removed |
m checking access date |
||
| Line 1: | Line 1: | ||
{{Short description|Software development methodology}} |
{{Short description|Software development methodology}} |
||
{{for| corporate communication topics|corporate identity|corporate design}} |
{{for| corporate communication topics|corporate identity|corporate design}} |
||
In [[software engineering]], '''CI/CD''' or '''CICD''' is the combined practices of [[continuous integration]] and either [[continuous delivery]] or [[continuous deployment]].<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-6- |
In [[software engineering]], '''CI/CD''' or '''CICD''' is the combined practices of [[continuous integration]] and either [[continuous delivery]] or [[continuous deployment]].<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-6-1|language=en}}</ref> |
||
This implementation, also known as the CI/CD pipeline, encompasses a culture, a set of operating principles, and a collection of practices that enables application development teams to deliver code changes on a nearly automated building, testing and deployment flow that is fast and reliable. Modern day [[DevOps]] practices involve continuous development, continuous testing, continuous integration, continuous deployment and continuous monitoring of software applications throughout the life cycle. The CI/CD practice, or ''CI/CD pipeline'', forms the backbone of modern day DevOps operations. |
This implementation, also known as the CI/CD pipeline, encompasses a culture, a set of operating principles, and a collection of practices that enables application development teams to deliver code changes on a nearly automated building, testing and deployment flow that is fast and reliable. Modern day [[DevOps]] practices involve continuous development, continuous testing, continuous integration, continuous deployment and continuous monitoring of software applications throughout the life cycle. The CI/CD practice, or ''CI/CD pipeline'', forms the backbone of modern day DevOps operations. |
||
Revision as of 16:44, 2 June 2021
In software engineering, CI/CD or CICD is the combined practices of continuous integration and either continuous delivery or continuous deployment.[1]
This implementation, also known as the CI/CD pipeline, encompasses a culture, a set of operating principles, and a collection of practices that enables application development teams to deliver code changes on a nearly automated building, testing and deployment flow that is fast and reliable. Modern day DevOps practices involve continuous development, continuous testing, continuous integration, continuous deployment and continuous monitoring of software applications throughout the 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-6-1.
{{cite news}}: Check date values in:|access-date=(help)
External links
- What is CI/CD - all you need to know by Maciej Manturewicz