Skip to content

Integrate SAP Cloud Platform Transport Management Into Your CI/CD Pipeline

Extend your CI/CD pipeline with SAP Cloud Platform Transport Management to add an enterprise-ready change and release management process and enable the transport of cloud-based applications on SAP Cloud Platform between several stages.


This procedure explains how to upload a multitartget application from a CI/CD pipeline to SAP Cloud Platform Transport Management and then import it into its target environment.

SAP Cloud Platform Transport Management allows you to manage the transport of development artifacts and application-specific content between different SAP Cloud Platform accounts. It adds transparency to the audit trail of changes so that you get information about who performed which changes in your production accounts and when they did it. At the same time, the Transport Management service enables a separation of concerns: For example, a developer of an application or SAP Cloud Platform content artifacts can trigger the propagation of changes, while the resulting transport is handled by a central operations team. For more information, see SAP Cloud Platform Transport Management.

The following graphic provides an overview about the interplay between continuous integration and Transport Management:

Interplay of CI and Transport Management



You can use this scenario to extend any CI process that meets the prerequisites, for example, the one described in Build and Deploy SAPUI5 or SAP Fiori Applications on SAP Cloud Platform with Jenkins.

The following graphic shows an example of the detailed procedure when combining continuous integration and SAP Cloud Platform Transport Management:

Detailed Procedure When Combining CI and SAP Cloud Platform Transport Management

The process flow contains the following steps:

  1. The CI server builds a multitarget application (MTA) archive.
  2. The MTA is uploaded into the import queue of the target node, which is specified in the CI pipeline (in this example, PRE-PROD).
  3. The release manager manually triggers or schedules the import, which results in the physical deployment of the MTA archive into the corresponding subaccount (in this example, PRE-PROD).
  4. As soon as the import is executed, a transport is triggered along the defined transport route so that the MTA archive reaches the import queue of the next node (in this example, PROD).
  5. There, the physical import into the corresponding subaccount can be either triggered manually by the release manager or automatically by using the scheduling mechanisms of SAP Cloud Platform Transport Management.



If you use the pipeline of the following code snippet, you only have to configure it in the .pipeline/config.yml.

Following the convention for pipeline definitions, use a Jenkinsfile, which resides in the root directory of your development sources.

@Library('piper-lib-os') _

piperPipeline script:this

Configuration (.pipeline/config.yml)

This is a basic configuration example, which is also located in the sources of the project.

    credentialsId: tms-secret-key
    nodeName: tms_target_node
    mtaPath: com.piper.example.tms.mtar
    customDescription: Custom-Transport-Description

Configration for the Upload to Transport Management

Parameter Description
credentialsId Credentials that are used for the file and node uploads to the Transport Management Service.
nodeName Defines the name of the node to which the *.mtar file is uploaded.
mtaPath Defines the path to *.mtar for the upload to the Transport Management Service.
customDescription Can be used as description of a transport request. Overwrites the default (Default: Corresponding Git Commit-ID).


For a detailed description of the relevant parameters, see tmsUpload.