Architecture Guide #26 • ABAP Cloud DevOps

SAP gCTS, abapGit & Clean Core CI/CD Pipeline Architecture Guide

A strategic DevOps guide on replacing classic CTS transports with Git-enabled Change and Transport System (gCTS), automated ATC quality gates, and CI/CD pipelines.

Interactive Pipeline Architect: Design your gCTS repository settings, configure multi-branch mapping, and generate your GitLab CI or GitHub Actions workflows with our In-Browser gCTS & CI/CD Architect.

1. The Shift from CTS to Git-Centric ABAP DevOps

For over 25 years, SAP development relied on the classic Change and Transport System (CTS / STMS). While CTS reliably moves data across homogeneous landscape tiers (DEV → QAS → PRD), it suffers from severe limitations in cloud-native software engineering:

No support for feature branches or distributed peer code reviews (Pull Requests / Merge Requests).
Transports are sequential and prone to "transport of copies" errors and overtaking collisions.
Inability to integrate with enterprise CI/CD runners (GitLab CI, GitHub Actions, Jenkins).

In ABAP Cloud Clean Core, SAP introduces gCTS (Git-enabled CTS) and native abapGit support, treating ABAP objects as version-controlled text files in Git repositories.

2. Architectural Landscape: Software Components as Repositories

In gCTS, the unit of version control is the Software Component (`SWC`):

Dimension	Classic CTS (STMS)	Clean Core gCTS
Unit of Change	Transport Request (`DEVK900123`)	Git Commit & Branch (`feature/order-api`)
Code Review	Manual review before release	Merge Request / Pull Request with diff viewer
Automated Quality Gate	Post-release ATC check	Pre-merge pipeline gate (blocking MR on ATC errors)
Rollback Strategy	Reverse transports (error prone)	Git revert / branch checkout

3. The Clean Core Automated CI/CD Pipeline

A production-grade ABAP Cloud pipeline executes three mandatory phases:

Pre-Merge Quality Gate: Whenever a Merge Request is opened, the CI runner invokes the ABAP Test Cockpit via REST API using check variant ABAP_CLEAN_CORE_DEVELOPMENT. If any priority 1 or 2 errors exist, the MR cannot be merged.
Automated Test Execution: Invokes ABAP Unit tests (`cl_aunit_runner`). Enforces code coverage thresholds (e.g. minimum 80% line coverage).
Automated Deployment (gCTS Pull): When the MR merges into main, the pipeline triggers a gCTS REST pull into the QA / Staging system.

Master Enterprise RAP & Clean Core Architecture

Get the complete 400+ page guide with end-to-end architectures, testing patterns, and migration blueprints:

Unlock Complete Enterprise Suite (80% Off • €9.80) → Also available in Paperback & Kindle on Amazon ($19.99)