Describing Continuous Integration, Delivery and Deployment

Note

In addition to Continuous Integration, Continuous Delivery, and Continuous Deployment, there are also others that exist, such as Continuous Testing or Continuous Development as an umbrella term.

However, the first three described concepts, which form the acronym CI/CD, are relevant in this lesson: "CI" stands for Continuous Integration, while the "CD" can stand for either Continuous Delivery or Continuous Deployment.

But before diving deeper, let's clarify the question: what is a pipeline? At its simplest, it is a series of activities that are carried out in a predefined order. Together, Continuous Integration, Continuous Delivery, and Continuous Deployment form the important concept of the CI/CD Pipeline with the goal of the best possible automation in software development and reduction of manual effort.

Putting all these pieces together, you can create a fully automated pipeline to build, test, and deploy your application.

In short, Continuous Integration (CI) is the adoption of agile principles while Continuous Delivery/Deployment (CD) is a combination of agile methodology techniques and a high-quality delivery process. The goal is to validate each change (commit), preferably in an automated way, so that it can be delivered in a reliable manner.

For more information about SAP Continuous Integration and Delivery service in SAP Discovery Center, see: https://discovery-center.cloud.sap/serviceCatalog/continuous-integration--delivery?region=all

More information: https://help.sap.com/viewer/8cacec64ed854b2a88e9a0973e0f97a2/Cloud/en-US/e9fa320181124fa9808d4446a1bf69dd.html.