GitLab
A hosted git service, on GitLab.com or self-managed, whose projects sit in groups that can be nested as subgroups up to 20 levels deep; the Git side for things here that commit SAP source pulled out of a tenant, a repository per object where that nesting allows one.
Where it sits
Used by
Optionally used: GitLab is set as the Git provider in Settings. The repository the extracted source files and version tags are committed to. On GitLab each iFlow gets its own repository, named group/packageId/artifactId.
Functional boundary
A pipeline that already promotes artifacts across tenants stays where it is; what CPIOps replaces is the work of building a pipeline just to get CPI artifacts into Git with history. If SAP ships native Git integration for the tenant, the documented answer is to stop using CPIOps, because the repository already holds the full commit history and nothing has to be migrated.
Connected from
data, outbound. Committing each artifact's extracted source files and tagging the commit with the artifact's CPI version, one repository per iFlow.
Functional boundary
A pipeline that already promotes artifacts across tenants stays where it is; what CPIOps replaces is the work of building a pipeline just to get CPI artifacts into Git with history. If SAP ships native Git integration for the tenant, the documented answer is to stop using CPIOps, because the repository already holds the full commit history and nothing has to be migrated.
Details
For your agent
- Ref
external:gitlab- JSON
- /externals/gitlab.json
- MCP
- Connecting an agent