Services / Cloud Infrastructure / Data, AI & Skills
Cloud Infrastructure · Data, AI & Skills

Ship SAP and cloud changes faster, with pipelines you can audit.

We build CI/CD pipelines and automation for SAP BTP apps, ABAP code, cloud infrastructure and custom applications, using SAP Continuous Integration and Delivery, GitHub Actions, Azure DevOps, AWS CodePipeline or Google Cloud Build. Changes move from developer to production through repeatable, tested and traceable steps, instead of manual transports and late night deployments.

2020SAP S/4HANA release where gCTS covers workbench and customising objects
3CI/CD options SAP documents for CAP apps on SAP BTP
5Systems in SAP's recommended ABAP environment DevOps landscape
Why it matters

Why SAP teams need DevOps

Many SAP teams still move changes by hand: transports released by email, BTP apps deployed from a laptop and cloud infrastructure built by clicking in a console. That works until something breaks in production and nobody can say exactly what changed. As SAP landscapes move to RISE with SAP, SAP BTP and hyperscaler services, the number of moving parts grows. Pipelines and automation make every change repeatable, tested and recorded.

Fewer manual errors

Automated builds, tests and deployments run the same way every time. Problems are caught in development, not after go-live.

An audit trail by default

Git history, pipeline logs and SAP Cloud Transport Management records show who changed what and when. Auditors get evidence without a spreadsheet hunt.

ABAP joins modern tooling

gCTS manages ABAP changes with Git, and abapGit moves code between systems outside the gCTS boundary. ABAP developers can work with the same practices as cloud teams.

Infrastructure as code

SAP landscapes on AWS, Azure and Google Cloud can be built with Terraform and Ansible, and SAP BTP accounts with the Terraform provider for SAP BTP. Environments can be rebuilt on demand.

What we do

What we do

We set up and run the pipelines and automation your SAP and cloud teams need.

01

CI/CD for SAP BTP apps

We set up SAP Continuous Integration and Delivery with predefined pipelines for CAP, SAP Fiori and SAP Integration Suite content. For more control, we build pipelines on GitHub Actions or with SAP Project Piper.

02

Transports with SAP Cloud Transport Management

We connect pipelines to SAP Cloud Transport Management so tested changes move into test and production subaccounts through approved routes. Each transport is recorded.

03

ABAP DevOps with gCTS and abapGit

We set up gCTS for SAP S/4HANA and the SAP BTP ABAP environment, with automated ABAP Unit and ATC checks. We use abapGit to move custom code from ECC to S/4HANA or to the cloud.

04

Infrastructure pipelines

We build Terraform and Ansible pipelines for SAP landscapes and surrounding cloud resources. We use SAP Deployment Automation Framework on Azure, AWS Launch Wizard for SAP and Google Cloud Workload Manager where they fit.

05

Pipelines for custom and non-SAP apps

We build CI/CD for web apps, integrations and services on Azure DevOps, GitHub Actions, AWS CodePipeline or Google Cloud Build and Cloud Deploy. Security scanning and approvals are part of every pipeline.

06

Operations automation

We automate routine SAP BTP tasks and alert responses with SAP Automation Pilot, and connect monitoring to SAP Cloud ALM. Recurring manual work shrinks.

How it works

How it works

  1. 1

    Assess

    We review how changes move today across ABAP, SAP BTP, infrastructure and custom apps. We identify the biggest risks and delays.

    1 to 2 weeks
  2. 2

    Design

    We define branching, environments, approvals and the toolchain for each type of change. We align it with your change management and audit requirements.

    1 to 3 weeks
  3. 3

    Build

    We set up repositories, pipelines, test automation and transport routes for a first application or landscape. We store secrets in the cloud's secret manager, never in code.

    3 to 6 weeks
  4. 4

    Expand

    We bring more applications, systems and teams onto the pipelines. We train developers and Basis staff along the way.

    4 to 8 weeks
  5. 5

    Run and improve

    We maintain pipelines, update tools and track deployment frequency and failure rates. We tune the process as your team matures.

    Ongoing
Across AWS, Azure and Google Cloud

Native DevOps services per cloud

We use SAP DevOps services together with the native tools of your cloud, or GitHub across all of them.

NeedAWSMicrosoft AzureGoogle Cloud
Build and deploy pipelinesAWS CodePipeline, AWS CodeBuildAzure Pipelines (Azure DevOps), GitHub ActionsCloud Build, Cloud Deploy
Infrastructure as codeAWS CloudFormation, TerraformBicep, TerraformTerraform, Infrastructure Manager
SAP landscape deploymentAWS Launch Wizard for SAPSAP Deployment Automation FrameworkWorkload Manager Guided Deployment Automation
Secrets for pipelinesAWS Secrets ManagerAzure Key VaultSecret Manager
Artifact and container registryAmazon ECR, AWS CodeArtifactAzure Container Registry, Azure ArtifactsArtifact Registry
Operations automationAWS Systems ManagerAzure AutomationWorkflows
For SAP landscapes

The SAP angle

SAP offers its own DevOps services on SAP BTP: SAP Continuous Integration and Delivery for predefined pipelines, SAP Cloud Transport Management for controlled transports, SAP Automation Pilot for operations tasks and SAP Cloud ALM for monitoring and change management. For ABAP, gCTS brings Git into the Change and Transport System, and abapGit handles code movement between systems, such as from ECC to S/4HANA. Under RISE with SAP, SAP runs the infrastructure, so pipelines focus on your code, configuration and BTP extensions. Where you run SAP yourself on a hyperscaler, infrastructure pipelines matter too, and we cover both.

  • SAP Continuous Integration and Delivery cannot be used with the SAP BTP ABAP environment, so we use Project Piper pipelines on a separate CI server there.
  • gCTS can use an SAP-managed Git repository or your own GitHub, GitLab or Bitbucket.
  • The Terraform provider for SAP BTP lets us create subaccounts, entitlements and services as code.
  • Clean core extensions on SAP BTP are easier to keep clean when every change goes through a pipeline.

© 2026 Mawkish Technologies. This guide, its diagrams and illustrations are protected by copyright. You’re welcome to learn from it and to quote it with credit and a link. Reproducing it, by hand or through AI, and publishing it as your own is not allowed. Read our copyright notice

What you get

Deliverables

  • DevOps assessment and target toolchain design
  • Working CI/CD pipelines for SAP BTP apps and custom applications
  • gCTS or abapGit setup with automated ABAP checks
  • Terraform and Ansible code for SAP BTP and cloud infrastructure
  • Transport routes in SAP Cloud Transport Management with approvals
  • Runbooks and training for developers and Basis teams
Questions

Frequently asked

Which CI/CD tool should we use for SAP BTP?

SAP Continuous Integration and Delivery is the quickest start, with predefined pipelines and no CI server to run. GitHub Actions or Project Piper give more flexibility if you already use them or need custom steps. We often combine them with SAP Cloud Transport Management for controlled releases.

Can we use Git for ABAP?

Yes. gCTS manages ABAP changes and transports using Git, covering workbench and customising objects from SAP S/4HANA 2020. In the SAP BTP ABAP environment, each software component maps to one Git repository. abapGit is used to move code outside that boundary, for example from ECC.

Does DevOps apply under RISE with SAP?

Yes, but the scope changes. SAP runs the infrastructure under RISE with SAP, so you do not automate VMs or databases. Your code, configuration, SAP BTP extensions, integrations and the cloud resources in your own account still benefit from pipelines.

Do we have to replace our current transport process?

No. We usually start by automating checks and BTP deployments alongside your existing transports, then extend step by step. Change Request Management in SAP Solution Manager 7.2 or SAP Cloud ALM can stay in charge of approvals.

Which cloud DevOps tool do you recommend?

We use what fits your estate: Azure DevOps or GitHub Actions on Azure, AWS CodePipeline on AWS, Cloud Build and Cloud Deploy on Google Cloud. GitHub Actions works across all three clouds and SAP BTP. The pipeline design matters more than the brand of tool.

The Corgate Check is our shorthand for looking after the details nobody sees in DevOps & Automation.

© 2026 Mawkish Technologies. This guide, its diagrams and illustrations are protected by copyright. You’re welcome to learn from it and to quote it with credit and a link. Reproducing it, by hand or through AI, and publishing it as your own is not allowed. Read our copyright notice