What is SAP Continuous Integration and Delivery? (2026)

What is SAP Continous Integration and Delivery

SAP Continuous Integration and Delivery (SAP CI/CD) is a fully managed service on SAP BTP that lets teams configure and run predefined pipelines. The pipelines automatically build, test and deploy code changes for SAP development scenarios such as CAP, SAP Fiori and SAP Integration Suite projects.

Continuous integration and continuous delivery are two software development approaches that improve code quality and speed up delivery. Both automate how teams build, test and release software, so developers can focus on writing code instead of repeating manual tasks. This guide explains CI and CD, what SAP Continuous Integration and Delivery offers, how it works, which pipelines it supports and where its limits are.

Table of Contents

What Is Continuous Integration (CI)?

Continuous integration is a practice in which team members integrate their work frequently, usually at least daily. An automated build, including tests, verifies each integration. The team then detects integration errors as early as possible.

Many teams find that CI reduces integration problems and lets developers work together more effectively. In practice, CI merges all developer working copies into a shared mainline several times a day. Each check-in triggers an automated build.

What Is Continuous Delivery and Continuous Deployment?

Continuous delivery (CD) extends CI. After each successful build, the team has a version that is ready to release. Teams produce application versions several times a day, spot bugs faster and release features as soon as they are ready instead of waiting for a big release cycle.

Continuous deployment goes one step further. The pipeline deploys every change that passes the automated tests to production without a manual approval step. Many organizations keep a manual approval gate before production, so they use continuous delivery rather than full continuous deployment.

What Are the Benefits of CI/CD?

CI/CD helps your organization deliver high-quality software faster and more reliably. The main benefits are:

Faster feedback: A problem in your code shows up sooner. Your team finds bugs, fixes them quickly and stops them from spreading through the codebase.
Better visibility: Automated tests tell you immediately if something goes wrong at any stage, such as during a new deployment.
Fewer manual errors: Automated build, test and deployment steps replace error-prone manual work.
Faster time to market: Teams release new features as soon as they are ready.

What Is SAP Continuous Integration and Delivery?

SAP Continuous Integration and Delivery is a service on SAP Business Technology Platform (SAP BTP). It runs in the Cloud Foundry environment. It lets you configure and run predefined CI/CD pipelines that build, test and deploy your code changes. The service connects to your Git repository, such as GitHub, GitLab, Bitbucket Server or Azure Repos.

You do not need to host your own Jenkins instance. The service also has a built-in integration with the SAP Cloud Transport Management service, which moves your code from one environment to another. You can read more about the platform in our article on what SAP Business Technology Platform is.

How Does SAP CI/CD Work?

You set up the service in a few steps:

Enable the service in the SAP BTP cockpit.
Assign the Administrator or Developer role to your user.
Add credentials so the service can clone your repository and deploy to SAP BTP.
Add your repository and create a webhook.
Create a job. You can use the Job Editor, an interactive UI, or write a YAML file in your source repository that follows SAP’s open-source project “Piper”.
Push a code change. The webhook triggers the build, test and deployment stages of your job.

Only administrators of the service can configure it. Developers then run and monitor the jobs.

Which Pipelines Does SAP CI/CD Support?

SAP Continuous Integration and Delivery offers predefined pipelines for designated SAP development scenarios. The table below lists the main ones. SAP adds pipelines over time, so check SAP Help for the current list.

Predefined pipeline	What it builds and deploys
SAP Cloud Application Programming Model (CAP)	CAP projects in the Cloud Foundry environment, including Node.js, Java and MTA-based projects
SAP Fiori in Cloud Foundry	SAPUI5 and SAP Fiori applications in the Cloud Foundry environment
SAP Fiori for the ABAP platform	SAPUI5 and SAP Fiori applications for the ABAP platform
SAP Integration Suite artifacts	Integration content in SAP Cloud Integration
Container-based applications	Docker images pushed to a container registry and deployed to SAP BTP

The CAP pipeline works for Node.js, Java and multitarget application (MTA) projects. This means SAP CI/CD supports Java-based CAP projects and SAP Fiori projects for the ABAP platform. It does not build every kind of ABAP or Java application.

SAP CI/CD vs Project Piper vs gCTS

These three tools solve different problems:

SAP CI/CD service: A managed service on SAP BTP with predefined pipelines and a UI.
Project Piper: SAP’s open-source tooling for continuous delivery. It gives more flexibility and works for projects on SAP BTP and on SAP on-premise platforms.
gCTS: The Git-enabled Change and Transport System manages version control for ABAP objects. Our guide on gCTS: SAP Git-enabled Change and Transport System explains how Git-based transport fits into a pipeline.

How SAP CI/CD Fits Into a Modern SAP Development Landscape

Teams increasingly pair CI/CD with cloud-native ABAP development. If you build on ABAP on Cloud, CI/CD pipelines let you ship changes to that environment safely and frequently instead of moving them through manual transports.

AI also speeds up this workflow. Our guide on how to accelerate SAP projects with AI covers how AI-assisted development changes ABAP coding and testing timelines.

What Should You Consider Before Using SAP CI/CD?

SAP CI/CD does not fit every landscape. Keep these limits in mind:

The service runs in the Cloud Foundry environment on SAP BTP, so you need a subscription and a supported region.
It offers predefined pipelines for designated scenarios. For other landscapes, such as on-premise systems, look at Project Piper.
It automates build, test and deployment, but it does not write your tests. Your team still needs a test strategy.

At MDP Group, we help teams move SAP development from manual transports to automated pipelines. We recommend that you start with one CAP or SAP Fiori project. Then extend the setup to other projects after the first pipeline runs stably.

Frequently Asked Questions

Does SAP CI/CD support both ABAP and Java applications?

Partly. The service offers a predefined pipeline for SAP Fiori projects on the ABAP platform and one for CAP projects, which can use Java. It does not cover every ABAP or Java scenario. Check the SAP Help list.

Is SAP CI/CD required for SAP BTP development?

No. It is not required, but it is a common approach for teams on SAP BTP. Automated builds and tests on every code change replace manual, error-prone deployment steps.

How does SAP CI/CD relate to gCTS?

gCTS manages version control for ABAP objects. SAP CI/CD orchestrates the broader pipeline of building, testing and deploying changes. Many teams use both together.

Do I need DevOps experience to set up SAP CI/CD?

Basic DevOps and CI/CD knowledge helps. The service offers predefined pipelines and a Job Editor, so the setup takes less work than building a pipeline from scratch.

Conclusion

SAP Continuous Integration and Delivery automates the build, test and deployment of your SAP code changes on SAP BTP. Start with a predefined pipeline for your CAP or SAP Fiori project. If you need support with SAP BTP development, contact MDP Group.