ci.runs.getOne run with its jobs and their steps, each with status and timing
Answers `{ run, jobs, steps }`. A failed step names its job; read that job’s log with `dcloud ci jobs logs`.
Request syntax
GET /ci/api/runs/{runId}Path parameters
runIdRequiredstring
Constraints: uuid
Response
200 with { run, jobs, steps }: the run as the list shows it (with waiting), its jobs (id, key, displayName, runsOn, needs, matrix, status, exitCode, error, runnerId, placement (where a runner pool machine ran it and why, e.g. "own host de1-host-1" or "cloud: de1-host-1 full (3 of 3 runner slots in use)"; null otherwise), outputs, startedAt, finishedAt, …) and the steps of every job (id, jobId, position, displayName, kind, status, exitCode, startedAt, finishedAt). 404 when the run is not in this organization.
A JSON response is wrapped as { "success": true, "data": … }; the CLI prints the whole body with --json.
Errors
- 400The request does not pass the schema above. The body is { "error": …, "issues": […] }, one issue per field.
- 401No credentials, or an access key that is unknown, revoked or expired.
- 403The caller's policies do not allow ci:GetRun on this resource. The body names the action and the resource, and the refusal is recorded in the audit log.
- 404The resource does not exist in your organization.
Examples
The required parameters only, with example values. Replace id and the other placeholders with your own.
dcloud ci runs get runIdcurl -X GET "https://console.platform.deutschecloud.app/ci/api/runs/runId" \
-H "Authorization: EWS-ACCESS-KEY $ACCESS_KEY"Generated from the API description, the same one the API checks requests against and the CLI is built from. MCP tool: dcloud_ci_runs_get.