CI/CD

In software engineering, CI/CD or CICD generally refers to the combined practices of continuous integration and either continuous delivery or continuous deployment.[1][2][3]

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.

For example, Akraino Edge Stack is a set of open infrastructures and application blueprints for the Edge, spanning a broad variety of use cases, and is delivered through CI/CD.[4]

In the context of corporate communication, CI/CD can also refer to the overall process of corporate identity and corporate design.

References
  1. Irani, Zubin (2018-03-28). "5 common pitfalls of CICD -- and how to avoid them". InfoWorld. Retrieved 2017-12-21.
  2. Heller, Martin (2015-07-20). "Continuous integration is not always the right answer. Here's why". TechBeacon. Retrieved 2017-12-21.
  3. Atlassian (2017-04-14). "Continuous integration vs. continuous delivery vs. continuous deployment". Atlassian. Retrieved 2019-04-04.
  4. https://wiki.akraino.org/display/AK/Akraino+Edge+Stack
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.