---
title: How to Configure CI/CD with SAP Continuous Integration and Delivery Service
description: Learn how to set up and configure CI/CD pipelines using SAP Continuous Integration and Delivery on SAP BTP.
---

[Learn SAP from the Experts | The SAP PRESS Blog](https://blog.sap-press.com)

# [How to Configure CI/CD with SAP Continuous Integration and Delivery Service](https://blog.sap-press.com/how-to-configure-ci-cd-with-sap-continuous-integration-and-delivery-service)

 Written by [SAP PRESS](https://blog.sap-press.com/author/sap-press) | Apr 22, 2025 1:00:00 PM

SAP Continuous Integration and Delivery lets you configure your CI/CD pipeline in the cloud to automatically build, test, and deploy your code with an easy-to-use configuration tool.

 

It also has a built-in integration with the SAP Cloud Transport Management service to transport the code from one environment to another. This tool is available in your [SAP Business Technology Platform](https://learning.sap-press.com/sap-btp) (SAP BTP) trial account under Extension Suite, and in the upcoming steps, you’ll subscribe to this service and configure your CI/CD pipeline.

 

 

The different stages of the pipeline can be configured in two ways:

- **Job Editor:** An interactive UI offered as part of SAP Continuous Integration and Delivery in SAP BTP to easily configure the different stages of the pipeline.
- **Source Repository:** Pipeline configuration will be manually entered in the *.yaml* file, which is based on SAP’s open-source project “Piper.”

In the following steps, you’ll configure the CI/CD pipeline using the graphical-based Job Editor:

1. Open your SAP BTP trial account, go to **Service Marketplace**, and search for “Continuous Integration and Delivery.”

1. Click on the tile to open the service, and click the **Create** button to subscribe to the service, as shown below.

1. Click **Create** in the popup to finalize.

1. Navigate to the **Users** node under **Security** to add SAP Continuous Integration and Delivery roles to your user in the SAP BTP account.

1. Click the user to navigate to the detail page, click the three-dot button, and choose **Assign Role Collection**, as shown in the next figure.

1. Select the **CICD Service Administrator** role, and click **Assign Role Collection**.

 

Now you have the authorization to access SAP Continuous Integration and Delivery.

1. Navigate to **Instances and Subscriptions** in your SAP BTP trial account, and open **Continuous Integration & Delivery** by clicking the highlighted icon.

1. You must add your GitHub credentials to connect to your repository from SAP Continuous Integration and Delivery. Open the **Credentials** tab, and click the plus icon, as shown below. SAP Continuous Integration and Delivery will use these credentials to access your private GitHub repository.

1. Enter the GitHub **Username** and **Password** (PAT), and then click **Create**.

1. Add another credential for your SAP BTP account to automate the [SAP Cloud Application Programming Model](https://blog.sap-press.com/introducing-the-sap-cloud-application-programming-model-cap) application’s deployment to the SAP BTP, Cloud Foundry environment, as shown below. You need to enter your SAP BTP account credentials here.

1. Navigate to the **Repositories** tab, and click the plus button to add your GitHub repository, as shown in the next figure.

1. Enter the GitHub repository URL, and select the GitHub credentials you created in the previous steps. Leave the other details as they are, which will generate a webhook that GitHub will use to trigger the CI/CD job. Click **Add** to create the repository.

1. Navigate to the **Jobs** tab, and click plus button to create a new CI/CD job.

1. Make the following configurations in the **General Information** section, as shown below. When the job is run, the service will fetch the source code from the Git repository capescalationjob from the branch main.

- - **Job Name**: Enter a unique Name for your CI/CD Job.
    - **Repository**: Select the GitHub repository you created in the **Repository**
    - **Branch**: Enter “main” (branch name of your Git repository).
    - **Pipeline**: Select **SAP Cloud Application Programming Model**.

1. In the **STAGES** section, ensure the **Configuration Mode** is set to **Job Editor**, which gives you the option to maintain the CI/CD pipeline using the UI editor from SAP Continuous Integration and Delivery. The other option is **Source Repository**, where you can maintain this configuration in your source code (SAP Cloud Application Programming Model application) instead of using the UI editor.

1. For **Build Tool**, leave **mta** as preselected.
2. Switch on the **Additional Unit Tests**, and leave **test** as the preselected value in the **npm Script** field. This will run the unit tests when the job is run. If the unit test fails, the job status will be set to **Failed**, and any further stages in the CI/CD pipeline won’t be executed.

1. Ignore the **Acceptance** and **Compliance** stage, and switch the **Deploy to Cloud Foundry Space** to **ON** in the **Release** stage. So, when the unit tests are run successfully, the application will be deployed to the Cloud Foundry space in SAP BTP.

1. To enter the details, navigate to your SAP BTP trial subaccount, and copy the **Org Name**, **API Endpoint**, and **Spaces** to the **Release** section in SAP Continuous Integration and Delivery.

1. Select the **cfdeploy** credentials that you created in the earlier steps, which will be used to authenticate the deployment of the application to the SAP BTP, Cloud Foundry environment. Click **Create** to save the job configuration.

 

For the Continuous Delivery process, you have the option to switch on the **Upload to Cloud Transport Management** to deploy the code in multiple environments (e.g., quality or production). For this example, leave this option switched off.

1. To manually trigger this job, click the **Trigger Build** button in the **Builds** section, as highlighted in this figure.

1. Click the build to open the log and wait until the status is successful, as shown in this figure.

1. Instead of running the CI/CD job manually every time after you save your source code in Git, you’ll configure GitHub to trigger the CI/CD job automatically using webhooks whenever the source code is updated in the Git repository. Navigate to the **capescalationrepo** in the **Repositories** tab, and choose **Webhook Data** to get the webhook details, as shown in the two figures below.

 

1. Go to your Git repository settings, click the **Webhooks** node, and choose **Add webhook** to add the webhook details from the previous step, as shown:

1. Copy all the details from the previous step, and click **Add webhook**, as shown in this figure.

1. To test this, let’s go to your source code in your [SAP Business Application Studio](https://blog.sap-press.com/what-is-sap-business-application-studio) development space and add a comment in your unit test file for pushing the code to the GitHub repository.

 

**Note:** In real-time, you’ll perform actual code changes to enhance or implement new features and push them to the Git repository to trigger the CI/CD process. For testing purposes, you’ll just add a comment to push the changes to the Git repository.

1. Commit the changes, and push them to GitHub:

`git add .`

`git commit -m ‘added a comment’`

`git push`

1. Open the job in SAP Continuous Integration and Delivery, and you can see a new build triggered, as shown in this figure.

 

If you want to configure the steps from the source code, choose **Source Repository** instead of **Job Editor** in the Configuration Mode field shown earlier.

Then you need to manually add the pipeline in your code by executing cds add pipeline in your project terminal, which will create a folder with the name *.pipeline* with the file *config.yaml*. You need to configure the CI/CD pipeline and its stages in this configuration file.

 

Congratulations! You’ve now successfully configured your SAP Cloud Application Programming Model application’s CI/CD pipeline using SAP Continuous Integration and Delivery in SAP BTP.

 

*Editor’s note*: This post has been adapted from a section of the book [*SAP Extension Suite Certification Guide: Development Associate Exam*](https://www.sap-press.com/sap-extension-suite-certification-guide_5490/?utm_source=sappressblog&utm_medium=referral&utm_campaign=Blogs&utm_term=2239&utm_content=2239) by [Krishna Kishor Kammaje](https://www.linkedin.com/in/kammaje/) and [Mahesh Kumar Palavalli](https://www.linkedin.com/in/maheshpalavalli/). Krishna is a passionate developer and application architect working at ConvergentIS. He is a recognized SAP Community contributor and was named as an SAP Mentor. Mahesh is a senior developer at SAP Labs in Bangalore. He has more than 9 years of experience working with customers from government and private sectors in the areas of SAP Fiori, SAP Business Technology Platform, and [ABAP](https://learning.sap-press.com/abap).

 

This post was originally published 4/2025.

[View full post](https://blog.sap-press.com/how-to-configure-ci-cd-with-sap-continuous-integration-and-delivery-service)

```json
{
  "@context" : "http://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "SAP PRESS"
  },
  "dateModified" : "2025-12-18T16:24:26.516Z",
  "datePublished" : "2025-04-22T13:00:00Z",
  "headline" : "How to Configure CI/CD with SAP Continuous Integration and Delivery Service",
  "image" : {
    "@type" : "ImageObject",
    "height" : 443,
    "url" : "https://5707200.fs1.hubspotusercontent-na1.net/hubfs/5707200/How%20to%20Configure%20CI_CD%20with%20SAP%20Continuous%20Integration%20and%20Delivery%20Service.jpg",
    "width" : 1440
  },
  "mainEntityOfPage" : "https://blog.sap-press.com/how-to-configure-ci-cd-with-sap-continuous-integration-and-delivery-service",
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "height" : 60.0,
      "url" : "https://cdn2.hubspot.net/hubfs/5707200/rheinwerk-sappress-logo.png",
      "width" : 312.23303
    },
    "name" : "Blog"
  }
}
```