Skip to Content

Build a Continuous Delivery Pipeline for SAP Cloud Application Programming Model

0 %
Build a Continuous Delivery Pipeline for SAP Cloud Application Programming Model

Build a Continuous Delivery Pipeline for SAP Cloud Application Programming Model

September 15, 2020
Created by
August 17, 2020
Use the SAP Cloud SDK Continuous Integration and Continuous Delivery toolkit for SAP Cloud Application Programming Model (CAP).

You will learn

  • How to set up a CI/CD pipeline for projects based on SAP Cloud Application Programming Model (CAP) on SAP Cloud Platform
  • How to set up Jenkins Server
  • How to deploy project on Cloud Foundry


CAP enables you to quickly create business applications by allowing you to focus on your business domain. It offers a consistent end-to-end programming model for full-stack development on SAP Cloud Platform.

You can use a sophisticated CI/CD pipeline without having to write or maintain the pipeline yourself. Rather, you can take advantage of the open sourced SAP Cloud SDK pipeline from project “Piper”, maintained by the SAP Cloud SDK team on GitHub.

Step 1: Create project based on SAP Cloud Application Programming Model

For local development, you need to install the cds command line tools once, which in turn require Node.js, as follows:

  1. Install Node.js from (use the latest LTS release).

  2. Install the cds development kit globally:

    npm i -g @sap/cds-dk
    cds  #> test-run it
  3. Get the sample project:

    cds init --add java,mta,bookshop

Please find more information about CAP in its documentation.

Log on to answer question
Step 2: Set up continuous delivery pipeline

SAP offers a pipeline which helps you to implement continuous delivery out-of-the-box. To add this pipeline to your project run the following command:

cds add pipeline

Now, you can see that your project contains two new files.

  • Jenkinsfile
  • .pipeline/config.yml or pipeline_config.yml in older versions of cds

The SAP Cloud SDK for Continuous Delivery is based on Jenkins. Jenkins offers the possibility to implement build pipelines as code. However, as explained before, you don’t have to write any line of code. As you can see in Jenkinsfile, the actual pipeline implemented as open source and executed here. We call this approach a centrally maintained pipeline.


Set pipelineVersion to a fixed released version (for example, “v34”) when running in a productive environment.

For available versions and release notes please visit:

You still want to control the behavior of this pipeline. Therefore, the command adds a configuration file in .pipeline/config.yml. Please note that in older versions of cds the file is named pipeline_config.yml and is located in the root of the project.

You can use the config.yml, for example, to control where to deploy your application productively. Of course, there are many more configuration options you can use to control the behavior of the pipeline. You will find more information about this in the pipeline documentation.

Now, you’ll need to push the code to a GitHub repository. This is required because the pipeline gets your code through Git. This might be GitHub, or any other cloud or on-premise Git solution you have in your company.

GitHub repository

Having an example ready which already contains the build pipeline, we need something to run the pipeline.

Log on to answer question
Step 3: Start Jenkins server

Next, start your build server instance. We’ll utilize the so called Cx-Server for that, which is developed by SAP’s project “piper”. It is based on popular and battle-tested open source components, such as Jenkins, Docker and Nexus. Thanks to the Cx-Server provided life-cycle management scripts, it is ready to work within a few minutes.

To start the build server, you just need a machine which has Docker installed. Create a new directory and initialize Cx-Server by using this docker run command:

docker run -it --rm -u $(id -u):$(id -g) -v "${PWD}":/cx-server/mount/ ppiper/cx-server-companion:latest init-cx-server

This creates a few files in your current working directory. The shell script Cx-Server and the configuration file server.cfg are of special interest.

Now, you can start the Jenkins server by using the following command:

chmod +x ./cx-server
./cx-server start

Congratulations! Your Jenkins is now starting up. Once it is running, you can open it by entering the IP or domain name of your host machine in your favourite browser.

If Jenkins asks you to login for creating a new job so in terminal run this command ./cx-server initial-credentials to find the default credentials.

IMPORTANT: We recommend to change the default password immediately.

Jenkins should welcome you with the following screen:

Jenkins Welcome

Next, you can continue with the basic setup and start building your project by adding your source code repository.

For configure the SAP cloud SDK Cx-Server, please follow the Cx-Server operations guide.

Log on to answer question
Step 4: Create Jenkins job

To create a build job for your project, navigate to New Item in the Jenkins main menu. On the following screen, choose Multi-branch Pipeline and specify a name for your project´s build job.

Jenkins Create Build

If your repository is set to private, please also create and use a pair of suitable credentials and choose them for your repository. If you are using, this will also protect you from running into rate limitations.

Next, you need to connect your project on Jenkins for running the build. Switch to Git and copy the URL of project repository. Look for Branch Sources at Jenkins screen and go to Add Source and add the link of your Git repository and click Save.

Jenkins will now scan your repository and trigger a build.

The best way to get an overview of the build status is to open the job, navigate to the currently running build, and open it in the blue ocean UI of Jenkins.

Jenkins Blue Ocean

Please have a look at this sample visual representation of the pipeline:

Cloud SDK
Did you change the Jenkins default password?
Step 5: Production deployment

As explained you can configure the behavior of the pipeline using the file .pipeline/config.yml. In this step, we will configure the production deployment as an example.

To deploy applications, you need to create a free trial account. You can create your account by visiting SAP Cloud Platform

After creating your account and activating it through email, you can log in to your personal SAP Cloud Platform Cockpit. For your first visit, it should look like this:

SAP Cloud Platform Cockpit first view

Now click the Home button in the upper navigation bar and then click Start Cloud Foundry Trial.

SAP Cloud Platform Cockpit start trial view

After selecting your region, your account will be automatically set up for development with Cloud Foundry.

Cloud foundry view

In order to deploy applications on SAP Cloud Foundry you need to provide the API endpoint and other properties. You can get them by going inside your trial.

Cloud foundry properties

Configure config.yml for Cloud Foundry settings.

   - space: 'my-space'
     org: 'my-org'
     credentialsId: 'credentials'
     apiEndpoint: '<Cloud Foundry API endpoint>'

Now you require credentials. It can be created in the Jenkins by navigating to Credentials > System > Global Credentials.

Jenkins System

On this screen, click Add Credentials and enter username, password, as well as an ID for your credentials record.

You can now leverage this credentials record by adding the credentials configuration property to the productionDeployment stage of your config.yml.

Pipeline will look like this after production deployment stage:

Production Deployment

For further details regarding stage production deployment, please refer to pipeline documentation.

For a detailed documentation of the individual properties please consult the Step documentation.

Log on to answer question
Step 6: Integrate Cloud SDK

You can add the following dependency to integrate Cloud SDK in your project.

Log on to answer question
Step 7: More information

This picture puts everything into context of the broader SAP ecosystem:

Cloud SDK

As you can see, SAP Cloud SDK is a natural companion for CAP applications, providing useful features like tight integration with SAP LoB solutions such as SAP S/4HANA and SAP SuccessFactors.

More detailed information on the qualities checked by the pipeline can be found here.

Log on to answer question

Next Steps

Back to top