Streamgraph · Diagram Design

Where the extra build minutes went

Weekly CI build minutes per pipeline, stacked on a symmetric baseline so the height of the whole stream is the week's total. The build roughly doubled in twelve weeks, from 124 to 278 minutes, and almost all of the growth is one layer: the end-to-end suite, up from 12 to 118 minutes a week.

Where the extra build minutes went Streamgraph of weekly CI build minutes by pipeline across twelve weeks, stacked on a symmetric baseline so the envelope height reads as the total; the end-to-end suite grows from 12 to 118 minutes a week and passes the unit suite in week eight, while the docs pipeline pauses to zero in weeks five and six. BUILD MINUTES PER WEEK END-TO-END PASSES UNIT W01 W02 W03 W04 W05 W06 W07 W08 W09 W10 W11 W12 LEGEND BUILD MINUTES PER WEEK BY PIPELINE · WEEKLY BUCKETS · SYMMETRIC BASELINE, ENVELOPE HEIGHT = WEEKLY TOTAL · ILLUSTRATIVE FIGURES, NOT A MEASURED PROJECT End-to-end · 688 min · focal Unit · 789 min Integration · 572 min Lint · 163 min Docs · 76 min · paused

FOCAL · END-TO-END

The end-to-end suite is the growth

12 minutes a week in week one, 118 in week twelve — it passes the unit suite in week eight and ends as the largest pipeline. Every other layer is roughly flat, so the widening of the whole stream is this one band widening.

The envelope is the total, by construction

Each week is centred on one midline, top and bottom of the stream averaging back to it, so the stream's height is the week's total at 1.25px per minute. The smoothing bends only the drawing between weeks — every vertex sits on its true stacked value, which is what the verifier checks.

The docs pinch is data, not a defect

The docs pipeline ran nothing in weeks five and six, so its band pinches to zero thickness and reopens. The zero weeks stay in the domain — resampling or bridging them would erase the pause the layer exists to show.

build minutes per week by pipeline · weekly buckets · illustrative example · diagram design