CI/CD
Sign in to saveAlso known as CICD
In software engineering, CI/CD or CICD is the combined practices of continuous integration (CI) and continuous delivery (CD) or, less often, continuous deployment. They are sometimes referred to collectively as continuous development or continuous software development.
In the Vinony graph
Vinony's link graph records 206 inbound references to CI/CD, and connects out to software development process, model-driven engineering and computer science.
It is catalogued under the topic Software development.
Vinony links it to 17 Wikipedia language editions.
~3 min read
Encyclopedic overview
6 sectionsContents
- Components
- Motivation
- Best practices for cloud systems
- See also
- References
- External links
In software engineering, CI/CD or CICD is the combined practices of continuous integration (CI) and continuous delivery (CD) or, less often, continuous deployment. They are sometimes referred to collectively as continuous development or continuous software development.
== Components == Continuous integration: Frequent merging of several small changes into a main branch. Continuous delivery: Producing software in short cycles with high speed and frequency so that reliable software can be released at any time, with a simple and repeatable deployment process when deciding to deploy. Continuous deployment: Automatic rollout of new software functionality.
Excerpted from Wikipedia’s “CI/CD” article, available under the CC BY-SA 4.0 licence.