CI Runs tab

The CI Runs tab of the CI/CD Pipelines screen (/pipelines?tab=ci-runs) is the complete history of every CI-triggered run, newest first.

Columns

Column	What it shows
State	The run’s current state (see below). A ⚠ note appears underneath when commit sync was skipped or a status push failed — hover it for the full message.
Pipeline	The mapping name, plus the CI build number when the pipeline sent one.
Branch / Commit	The branch and short commit from the trigger payload. Shows — when the trigger didn’t include them (for example a plain CLI trigger).
Result	Passed / total, with failures called out in red.
Duration	How long the run took, from trigger to finish.
Triggered	How long ago, and which CI token or CLI started it.
Links	↗ opens the CI build in your CI platform; the rocket opens the full Testver report in Results.

Run states

State	Meaning
queued	Accepted and waiting for a free execution slot; the position is shown next to the state. CI runs execute one at a time.
running	Executing on the Testver server right now.
passed	Finished with no failures — the build was gated green.
failed	Finished with failures — the build was gated red.
cancelled	Cancelled from the CI job, the CLI (Ctrl-C), or the API.
error	Could not complete: the target stayed busy past the retry window, no result was recorded, or a queued run was lost to a server restart.

Filters

Four controls narrow the list: state, pipeline, environment, and a free-text branch box. The heading shows how many runs match (3 of 24), and ✕ Clear resets all four at once.

Filters are stored in the address bar, so a filtered view can be bookmarked or pasted to a colleague — for example /pipelines?tab=ci-runs&pipeline=pr-gate-main&state=failed.

Tip

You usually don’t need to set these by hand. Clicking any row in Insights on the Dashboard opens this tab already filtered to that pipeline, branch, or environment.

CI runs vs test runs

A CI run is the trigger record — who asked for it, for which commit and build, and what state it reached. The test run is the execution itself, with the tests, artifacts, and analysis, and lives in Results.

The rocket link connects them. Going the other way, a CI-triggered run in Results carries a CI badge and a CI build link, so you can hop between the pipeline and the report from either side.

Related

• CI/CD Pipelines overview — how triggering and gating work.
• Dashboard tab — summaries and click-through filtering.
• Trace tab — find the runs that gated a specific commit.
• Results — the full report behind each row.