Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.



Company
Cherrywork Digital Applications
Digital and AI
SAP Services
Industries
Resources

Cherrywork.com

SAP CLOUD INTEGRATION CI/CD USING GITLAB

WRITTEN BY

Anitha K
PUBLISHED​
1st June 2022

INTEGRATION

SHARE

In this blog I have explained how to deploy and run CI/CD pipeline for SAP Cloud Integration artifact using GitLab. By the end of this article you would be able to deploy a basic CI/CD pipeline for your artifact.

pre-requisite:
1. SAP Cloud Integration trial account.
2. An existing cloud integration flow.
3. GitLab with an active runner.

1. Create a new project in GitLab:

Menu

2. Modify the YAML config file :
Update the YAML file to deploy the integration artifact using Piper.
Piper is an open source tool to implement continuous delivery.

view merged YAML

Replace the “CREDENTIALS” value as explained below:
Go to your SAP BTP trial account > select your API instance (create a new instance, if not already done)> click on the service keys > copy the entire credentials.

{
“oauth”: {
“clientid”: “xx-xlkjjfd-asd-xxxx-0000-xxxxxx!0000|it!sssss”,
“clientsecret”: “12345–6788–45rt-adcd-asdgthkjfn_xxxxxxxxxxxx”,
“url”: “https://3xxxxxxxx.it-cpitrialxx.cfapps.us10-001.hana.ondemand.com“,
“tokenurl”: “https://3xxxxxxxx.authentication.us10.hana.ondemand.com/oauth/token
}
}

Replace the “maildemo” with your actual Iflow ID

bin/piper integrationArtifactDeploy –verbose –apiServiceKey $(CREDENTIALS) –integrationFlowId “maildemo”

deployment status

3. Run the pipeline
Click the commit changes as shown below to run the pipeline.

project information

4. Pipeline successfully triggered:
Once the pipeline is passed successfully you can see the status as shown below.

Update gitlab ci.yml file
5. Validate flow deployment Once the pipeline is successful it will trigger the respective Cloud integration flow “maildemo”
maildemo
From the above snapshot we could conclude that whenever the pipeline runs successfully in the GitLab, it will automatically trigger the respective cloud integration flow.
Related Stories
Security Spotlight: Why Staying on SAP PI/PO Puts Your Data at Risk

Security Spotlight: Why Staying on SAP PI/PO Puts Your Data at Risk

SAP Process Integration (PI) and Process Orchestration (PO) have long been the backbone of integration and orchestration for SAP landscapes. They serve as the central platforms for integrating various SAP and non-SAP systems, managing workflows, and orchestrating business processes across the enterprise.