Promotion thresholds
The warning/failure durations that decide whether a promotion leg is shown as on target, slow, or over.
Overview
On the Versions lookup and aggregates pages, every leg of a commit's journey to prod — and the end-to-end total — is colored by comparing how long it took against two thresholds: a warning threshold (exceeding it marks the leg "slow") and a failure threshold (exceeding it marks the leg "over target").
These are deliberately generous initial estimates and are expected to be tuned as real latency data accumulates. The values below are rendered directly from the source of truth in code, frontend/models/version_lifecycle.go.
Config version thresholds
Applied to sdp-pipelines config versions: the per-service-group timeline shown for an sdp-pipelines commit.
| Leg | On target (≤) | Slow (≤) | Over (>) |
|---|---|---|---|
| commit → int | 1h | 4h | 4h |
| int execution | 1h | 2h | 2h |
| int → stg | 8h | 1d | 1d |
| stg execution | 1h 30m | 3h | 3h |
| stg → prod | 1d | 3d | 3d |
| prod execution | 2h | 4h | 4h |
| total (commit → prod) | 2d | 4d | 4d |
Component image thresholds
Applied to component image commits, whose journey has no per-environment execution phases — only the wait to reach each environment.
| Leg | On target (≤) | Slow (≤) | Over (>) |
|---|---|---|---|
| commit → int | 8h | 1d | 1d |
| int execution | 1h | 2h | 2h |
| int → stg | 1d | 3d | 3d |
| stg execution | 1h 30m | 3h | 3h |
| stg → prod | 1d | 3d | 3d |
| prod execution | 2h | 4h | 4h |
| total (commit → prod) | 2d | 4d | 4d |
Color semantics
- green at or under the warning threshold (on target).
- yellow over warning, at or under failure (slow).
- red over the failure threshold.
- blue the leg is still in progress (no finish yet).
- gray no data, or no threshold applies to the leg.