Testing and CI

CI pipeline

This page is an index. CI is documented on nine pages, one per reader job. Open the page that matches your task.

For the published-upgrade regression gate, see selection and routing, runner budgets, and Package Acceptance baselines. Weekly validation is listed under Update Migration.

Docs-only main pushes skip CI. Every canonical main push admitted by the CI workflow selects the published-upgrade regression gate.

Page Read it when
CI pipeline jobs The job table, the fail-fast order, and the Control UI size budgets.
Watch a CI run Wait on one pull request head, recover a stuck run, and pass the evidence gate.
CI checkout ownership Shared checkout anchors, fetch retry budgets, and trusted action policy.
CI scope and routing Why a job did or did not run: changed-scope detection and manual dispatch.
CI runner classes Trust-based runner routing, Blacksmith classes, and runner backend modes.
CI capacity and shard weights The runner registration budget and the measured timings behind shard packing.
Release validation workflows Full Release Validation, live and E2E shards, Package Acceptance, install smoke, Docker E2E, and Plugin Prerelease.
Scheduled and maintenance workflows OpenClaw Performance, QA Lab, CodeQL, the maintenance jobs, and ClawSweeper activity forwarding.
Local checks and Testbox Reproduce a lane locally, keep the shrink-only ratchets, and run Crabbox or Testbox proof.

Where each section moved

Every section heading from the previous single-page version keeps its anchor here, so an existing link such as /ci#pipeline-overview still resolves. Each entry points at the page that now holds the content.

Was this useful?
On this page

On this page