Marimekko · Diagram Design

One pipeline on one runner is a fifth of all CI time

10,000 CI minutes over 30 days, five pipelines wide and up to three runner operating systems tall. The mobile pipeline is a quarter of the bill, and 83% of it runs on macOS — one segment that is a fifth of everything.

One pipeline on one runner is a fifth of all CI time Marimekko chart of 10,000 CI minutes over 30 days, split five pipelines wide and up to three runner operating systems tall; column width is each pipeline's share of all minutes, segment height is each runner's share within its pipeline, and the mobile pipeline's macOS runners alone account for about 20 percent of the total. Linux 2,140 min · 68% macOS 380 min · 12% Windows 620 min · 20% Linux 2,460 min · 88% Windows 340 min · 12% Linux 420 min · 18% macOS 1,980 min · 83% of mobile Linux 1,120 min · 80% Windows 280 min · 20% i web · 31% api · 28% mobile · 24% infra · 14% docs · 3% LEGEND WIDTH = PIPELINE SHARE · HEIGHT = RUNNER SHARE WITHIN PIPELINE · AREA = SHARE OF ALL CI MINUTES · 30 DAYS · 10,000 MIN · ILLUSTRATIVE FIGURES mobile × macOS · the focal segment Linux macOS Windows i docs · 260 min on Linux, 2.6% — too narrow to label

One segment carries the story

mobile × macOS is the focal segment because it is the finding, not because it sorts first. Width says mobile is 24% of all minutes; height says 83% of those are macOS; the area is the 20% of the whole those two numbers multiply to.

How to read it

Read across for the pipeline mix, down for the runner mix within a pipeline, and by area for the joint share. Every column is the full plot height, so a segment's height is always a share of its own column, never of the whole — that is what the area is for.

What the chart doesn't show

Minutes, not cost or count. macOS runner minutes are billed at a multiple of Linux, so the macOS segments understate spend; and a wide column can be a few long jobs or many short ones. The figure shows where time goes, not why.