CI/CD

From Wikipedia, the free encyclopedia

This is an old revision of this page, as edited by Jen67uv56 (talk | contribs) at 17:11, 27 August 2021 (Undid revision 1040950342 by MrOllie (talk) Keeping in line with the format found on the DevOps page). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

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

  1. ^ Sacolick, Isaac (2020-01-17). "What is CI/CD? Continuous integration and continuous delivery explained". InfoWorld. Retrieved 2021-06-01.

Further reading