Dashboardblocks
Components

Deployments

Recent deploys, environments and what is waiting to ship, DORA metrics and build health.

Deployment blocks show what shipped, where it's running and how healthy the pipeline is. Statuses (ready, failed, running, queued and rolled back) each have an icon and a label, and the running spinner stops for reduced motion. DORA metrics are rated against the widely used elite, high, medium and low bands; bands differ between reports, so adjust getDoraLevels to yours. Pass fixed dates, so the blocks render the same on the server and in the browser.

Recent Deployments

The latest builds with their commit, environment, author, how long they took and their status.

Deployments
The latest builds across environments
  • Fix currency rounding on invoicesRunning
    Production9f3c2a1Ana Limarunning for 1m 34s
  • Fix currency rounding on invoicesReady
    Preview9f3c2a1Ana Limatook 3m 32s
  • Add retry to webhook deliveryReady
    Production41be08dKenji Moritook 3m 07s
  • Upgrade image pipelineRolled back
    Productionc07d9e4Sara Okafortook 1m 06s
  • Upgrade image pipelineFailed
    Previewc07d9e4Sara Okafortook 2m 23s

Environments

What each environment is running and how many commits are waiting to be promoted to the next.

Environments
What each environment is running, and what is waiting to be promoted
  1. DevelopmentReady
    v3.2.0-rc.49f3c2a1Ana Lima,
  2. 4 commits waiting to be promoted from Development
    StagingReady
    v3.2.0-rc.241be08dKenji Mori,
  3. 2 commits waiting to be promoted from Staging
    ProductionReady
    v3.1.47a21c5eSara Okafor,

Delivery Performance

The four DORA metrics with their band and the change on the period before, in the direction that's better.

Delivery performance
Last 30 days, against the 30 days before
Deployment frequencyElite
3.4/day
↑ 31% better, was 2.6/day
How often you ship to production
Lead time for changesElite
19 h
↓ 30% better, was 27 h
Median time from commit to production
Change failure rateHigh
8%
↓ 27% better, was 11%
Share of deployments causing a failure
Time to restoreHigh
2.5 h
↑ 39% worse, was 1.8 h
Median time to restore after a failure

Build Health

The last runs of each pipeline as a strip, with the pass rate and median duration.

Build health
The last 30 runs of each pipeline, oldest on the left
  • main93% passed · 6m 52s median
    28 of 30 finished runs passed, 2 failed.
  • release100% passed · 23m 06s median
    29 of 29 finished runs passed, 0 failed, one is running.
  • nightly e2e73% passed · 48m 24s median
    22 of 30 finished runs passed, 8 failed.
  • docs100% passed · 3m 48s median
    30 of 30 finished runs passed, 0 failed.

On this page