Change promotion

Moving a change through the environments of a landscape, from development through test to production, and knowing which change has reached which environment. A CI/CD pipeline builds and tests on each source change, deployment puts a build onto its runtime, and getting source into git is source control.

Overview

SAP SHIPS

capire's CI/CD guide deploys to a staging subaccount on a push to the main branch and to a separate production environment when a release is published, with the target account in repository or organisation variables. A CAP project built as a Multitarget Application can also be promoted through SAP Cloud Transport Management, to which SAP Continuous Integration and Delivery uploads the archive.

Not covered: At the pipeline's convention: which branch or release reaches which subaccount is the workflow's. The upload to the transport service is documented for SAP's CI/CD service in SAP Learning; the parts of capire's CI/CD guide quoted here do not name the transport service.

SourceDeploy using CI/CD Pipelines, capirechecked
THE COMMUNITY ADDS

No community artifact is documented here.

Artifacts1

1 of 1 artifacts
ArtifactSignals
CLI tools1
git-env-branchesGeneralShows which feature branches reached which environment branch
Signals
Functional boundary

Details

Coverage
statecore only, CAP
assessed
also inABAP, BTP/BAIP, UI5
For your agent
Ref
capability:change-promotion
JSON
/capabilities/change-promotion.json
MCP
Connecting an agent