Skip to content

Latest commit

 

History

History
 
 

CICD-UploadIntegrationArtefact

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 

CICD - Upload Integration Artefact

| Recipes by Topic | Recipes by Author | Request Enhancement | Report a bug | Fix documentation |

Mayur Mohan Belur Mayur Mohan Belur

This CICD Jenkins job allows you to checkout the latest version of the configured integration flow artefact from your source code repository and either update or create the artefact on the Cloud Integration tenant. Optionally you can also deploy the integration flow artefact and retrieve the deployment status.

A typical flow would look something like this:

  • You create a new integration flow on your Cloud Integration development tenant.
  • You download the integration flow into your source code repository to do security checks or to merge it with other resources that have been worked upon outside of Cloud Integration.
  • Using this job you can upload the integration flow to your Cloud Integration test tenant.
  • You perform some tests on your test tenant.

Instructions to consume the CICD Jenkins file

Environment Variables List

Configure the following environment variables before executing the Jenkins Job

Name Example Description
IntegrationFlowID "IntegrationFlow1" The ID of the integration artefact that shall be uploaded to the configured Cloud Integration tenant
IntegrationPackage "CICD" The ID of the integration package. In case the integration flow artefact does not exist in the Cloud Integration design time yet, for the first upload an integration package has to be specified, so that the integration flow can be added there. If it already exists in the design time, this parameter can be ignored.
DeployFlow true
false
Based on this flag, after the upload the integration flow artefact will be deployed to the Cloud Integration tenant runtime
DeploymentCheckRetryCounter 20 Specify the maximum count of retries checking for a final deployment status as the deployment of the integration artefact might take a few seconds. Between each check we'll wait for 3 seconds
CPIHost "${env.CPI_HOST}"
Neo: "xxxxxx-tmn.hci.eu2.hana.ondemand.com"
CF: "xxxxxx.it-cpi001.cfapps.eu10.hana.ondemand.com"
The host name (without HTTPS) of your Cloud Integration tenant
CPIOAuthHost "${env.CPI_OAUTH_HOST}"
"xxxxxx.authentication.sap.hana.ondemand.com"
The host name (without HTTPS) of the OAuth token server of your Cloud Integration tenant
CPIOAuthCredentials "${env.CPI_OAUTH_CRED}"
"CPIOAuthCredentials"
The alias of the OAuth credentials for the Cloud Integration tenant which is deployed on your build server (like Jenkins)
GITRepositoryURL "${env.GIT_REPOSITORY_URL}"
"github.com/CICD/integrations.git"
The full URL of the source code repository without HTTPS
GITCredentials "${env.GIT_CRED}"
"GIT_Credentials"
The alias of the source code repository credentials which is deployed on your build server (like Jenkins)
GITBranch "${env.GIT_BRANCH_NAME}"
"refs/heads/master"
Specify the source code repository branch that you want to work with
GITFolder "IntegrationContent/IntegrationArtefacts" Specify the folder structure in your source code repository from where you like to read the integration artefact

Related Recipes

References