Deployments view

Where rollouts live.

Listing

The Deployments page lists every deployment, newest first and filterable by state, showing the artifact build number, audience summary (channels and groups), strategy, percentage, state and creation time.

The project page carries a summary card. Active and paused deployments always appear there, however much history sits above them, because a live rollout should never be below the fold.

A deployment is in one of five states: draft, active, paused, completed or cancelled. See Deployments for what each one means for the devices checking in.

Detail page

Counters refresh on their own, every few seconds, without a page reload:

• Offered: devices that were handed the build, meaning eligible and inside the cohort cutoff.
• Downloaded: reported the binary as fetched.
• Confirmed: booted the new build and confirmed it.
• Failed: reported a terminal failure.
• Rolled back: took the update, failed validation, and reverted.
• Pending: offered, with no terminal status reported yet.

Counts come from what devices report to /api/v1/ota/status/.

Controls

Which controls appear depends on the state. Everything else about a deployment is immutable: to change the audience or the artifact, create a new one.

Control	Shown when	Effect
Start	draft	Begins offering the build.
Resume	paused	Same button, resumes offering.
Pause	active	Stops offering immediately.
Complete	active or paused	Retires the deployment as finished.
Cancel	anything not already completed or cancelled	Retires it as abandoned.
Ramp	active or paused, canary only	Raises the rollout percentage.

Two things worth knowing:

• The dashboard shows the rollout control for canary deployments only. An immediate deployment goes to its full audience when it starts, so there is nothing to ramp. The API is looser: {"action": "ramp"} raises the percentage on any deployment, whatever its strategy or state.
• Ramping only goes up. A percentage below the current one is refused, in the dashboard and the API alike, so you cannot accidentally shrink a rollout that devices have already been offered. Pause instead.
• Cancel works at any percentage, including 100%, for as long as the deployment is live. It is the stop button for a bad build.

Per-device drill-in

Click through a counter to see the underlying device list, which is what you want when investigating failed installs. The reported reason and timestamp are preserved per device.