| Recipes by Topic | Recipes by Author | Request Enhancement | Report a bug | Fix documentation |
 |
Axel Albrecht |
|---|
This CICD Jenkins job allows you to check the Cloud Integration tenant for a new version of your integration artefact and if a new version exists, it downloads and stores it in a source code repository like Git.
A typical flow would look something like this:
- Create a new integration flow in Cloud Integration web tooling and store it in the source code repository like Git. Refer related recipes section for this.
- Continue working on the integration flow in Cloud Integration and whenever major building blocks are done save a new version of the flow.
- Whenever the pipeline job is running, and there is a newer version of integration flow available in Cloud Integration tenant than the integration flow will be downloaded and stored in the source code repository like Git.
Instructions to consume the CICD Jenkins file
Configure the following environment variables before executing the Jenkins Job
| Name | Example | Description |
|---|---|---|
| IntegrationFlowID | "IntegrationFlow1" |
The ID of the integration artefact for which you want to download the updated version |
| 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 where you like to store the integration artefact |
| GITComment | "Integration Artefacts update from CICD pipeline" |
Specify the text to be used during check-in to your source code repository |