SAP Cloud ALM
SAP Cloud ALM test repository adapter for ABAP Agent 2.0 — CLI and Guides references.
Use adapter type calm to connect SAP Cloud ALM so the agent can search test cases for your pipeline.
When you create the ABAP pipeline with pipeline set, leave --labid unset unless you deliberately need to override it. The agent derives the default lab ID as <QAS SID> <QAS RFC hostname>. Casual overrides can break Test Cycles in SeaLights. See Create and list pipelines.
Configure
Configure Test Repositories —
slabapcli testrepo set --type calmSetup and installation (Part 1)
Show the value with Test Cycles (Part 2)
testrepo set parameters for calm
Non-secret keys use --setting key=value. Secrets are entered interactively (not via --setting). Plus common options (--name, --type, --pipeline, --test-stage) — see Configure Test Repositories.
Authentication uses the OAuth client-credentials flow: clientId and clientSecret.
Alternatively, use --servicebinding (CALM only) to paste SAP BTP service binding JSON interactively. That flag replaces tokenUrl, apiBase, clientId, and clientSecret — do not pass those keys as --setting when you use --servicebinding.
tokenUrl
Setting
Yes*
UAA base URL from the service binding uaa.url (/oauth/token is appended when missing).
apiBase
Setting
Yes*
API gateway URL from the service binding endpoints.Api (/api is appended when missing).
searchPaths
Setting
No
Comma-separated list that scopes the search. Written as top-level searchpaths in config.toml.
confidenceThreshold
Setting
No
Integer 0–100. Minimum confidence for a match. When omitted, the adapter uses 0.
clientId
Secret
Yes*
OAuth client_id for the client-credentials flow.
clientSecret
Secret
Yes*
OAuth client_secret for the client-credentials flow.
*Required when you configure connection fields manually. Omitted when you use --servicebinding (values are taken from the pasted JSON).
Supply connection fields with --setting, or use --servicebinding to paste SAP BTP service binding JSON interactively (CALM only; replaces tokenUrl, apiBase, clientId, and clientSecret).
--test-stage is optional. See Configure Test Repositories for the default "{type} Tests" value, clear-on-omit behavior, and duplicate-stage warning.
When you use manual --setting values, the CLI prompts for clientId and clientSecret interactively (OAuth client-credentials flow; secrets are not accepted via --setting). Do not combine --servicebinding with --setting tokenUrl, apiBase, clientId, or clientSecret.
Once the test repository is configured and the connection test succeeds:
Finish any remaining agent setup for the pipeline (RFC, pipeline, additional test repositories) if you have not already.
Schedule repository search with
search_testrepo.Capture coverage with Footprints and your test runs.
For the full setup order, see Start the ABAP Agent Server and Configure Test Repositories.
search_testrepo registers a Windows Scheduled Task that runs watcher.exe SEARCH_TESTREPO on a cron schedule.
--pipeline
Yes
Pipeline name ([[pipeline]].name).
--testrepo
Yes
Test repository name ([[testrepo]].name) linked to that pipeline.
--cron
No
5-field cron expression in the machine's local time. Default: 0 2 * * 0 (Sunday at 02:00). Supported forms: M * * * *, */N * * * *, M/N * * * *, M H * * *, and M H * * D (D is one day, 0-7 or SUN-SAT). Ranges and lists (for example 1-5) are not supported, and day-of-month and month must be *.
Full command reference (stop, list, prerequisites): Search Test Repositories.
SeaLights associates test executions with ABAP code changes through Footprints on the agent side.
Schedule Footprints for the pipeline
This creates a FOOTPRINTS scheduled task that periodically collects coverage-related data and sends it to SeaLights. Full syntax and stop command: Collect Footprints data for your Pipeline.
Last updated
Was this helpful?