| Recipes by Topic | Recipes by Author | Request Enhancement | Report a bug | Fix documentation |
 |
Mayur Mohan Belur |
|---|
This CICD Jenkins job allows you to deploy an integration flow, check its deployment status and the MPL (message processing log) status of the message that gets automatically performed after the deployment due to a scheduler configuration or the consumption of files from an (S)FTP server or messages from a JMS queue.
In case of a successful message processing the job then downloads the integration flow artefact from the Cloud Integration tenant and commits it to the source code repository. In case of a failure during deployment or during message processing the job will provide you the error details.
A typical work flow would look something like this:
- You have uploaded an integration flow to your Cloud Integration test tenant.
- Using this job the integration artefact will be deployed and a message will automatically be launched.
- The job will provide you the log status.
- If the message processing was successful the job will download the integration flow and store it into your source code repository.
- The stored integration flow can be deployed to a productive Cloud Integration tenant.
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 that shall be deployed to the configured Cloud Integration tenant |
| FailJobOnFailedMPL | true false |
Specify if the job should fail in case the status of the retrieved message processing log is Failed or Retry. If you are doing negative testing and you're expecting the integration artefact run to fail, set this to "false" |
| 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 |
| MPLCheckRetryCounter | 10 |
Specify the maximum count of retries for checking the final MPL status as the process might run for a while. 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 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 |