Skip to content


This stage is responsible to release/deploy artifacts into your productive landscape.

Stage Content

This stage comprises following steps which are activated depending on your use-case/configuration:

step step description
cloudFoundryDeploy For Cloud Foundry use-cases: Performs deployment to Cloud Foundry space/org.
githubPublishRelease Publishes release information to GitHub.
healthExecuteCheck Performs health check in order to prove that deployment was successful.
kubernetesDeploy For Kubernetes use-cases: Performs deployment to Kubernetes landscape.
multicloudDeploy Can perform both to cloud foundry and neo targets. Preferred over cloudFoundryDeploy and neoDeploy, if configured.
neoDeploy For Neo use-cases: Performs deployment to Neo landscape.
npmExecuteEndToEndTests Executes smoke tests by running the npm script 'ci-smoke' defined in the project's package.json file.
tmsExport For TMS use-cases: Performs export to Transport Management Service node
tmsUpload For TMS use-cases: Performs upload to Transport Management Service node
transportRequestUploadCTS This step uploads SAPUI5 application to the SAPUI5 ABAP repository.

Stage Activation

This stage will be active if any one of the following conditions is met:

  • Stage configuration in config.yml file contains entries for this stage.
  • Any of the conditions are met which are explained in the section Step Activation.

Step Activation

For this stage no conditions are assigned to steps.

Additional Stage Parameters

name mandatory default possible values
script yes
  • script - The common script environment of the Jenkinsfile running. Typically the reference to the script calling the pipeline step is provided with the this parameter, as in script: this. This allows the function to access the commonPipelineEnvironment for retrieving, e.g. configuration parameters.

Configuration of Additional Stage Parameters

The stage parameters need to be defined in the section stages of config.yml file.