Cross-section

160 deploys in 26 days, written down the way a tree writes down its years. The date runs from the pith to the bark, the time of day runs around the circle, and every pale notch is a real deploy from the log.

Touch a ring or scroll: the trunk will grow out from the pith.

See the sites off this pipeline

10 October

The pith

Day one: 2 deploys. The very first was the folio project, commit bcede65. The camera is where the whole pipeline still fits under one finger.

11 October

The first wide ring

The next day, 26 deploys. A ring thickens from the count alone: the tree has no idea whether a day mattered, it just keeps score.

17 October

A second growth spurt

22 deploys, and 4 of them left knots. A wide ring is not a clean one: the faster a trunk grows, the more often it picks up flaws.

19 October – 25 October

Drought

7 days in a row without a single deploy. The rings are thin, but they are there: the calendar keeps going without us. 12 of 26 days are empty overall.

The whole slice

Night

The sector from 22:00 to 04:00 UTC holds no notch at all: 6 hours of the day are empty across the entire log. In Kyiv that is the dead of night. That sector is lit up now, and the drying crack lies right inside it.

The whole slice

19 knots

Here the gates had passed, the site was live, and the check of the live address found an error. A trunk does not hide that: the rings bend around the knot. 14 of 19 have a later clean deploy of the same project.

4 November

The bark

The last day in the log: 44 deploys, the thickest ring. 90 380 gate checks and 55 projects altogether, all in one trunk.

See the sites off this pipeline

Every ring

Each row is a day, the bar is the number of deploys. Press one and the slice shows that ring.

Every knot

Deploys after which the check of the live address found errors. Their number is on the right.

How it is made

There is no geometry: one triangle and a WebGL2 fragment shader. Each pixel finds its own day from the radius and its own minute from the angle.
The data sits in a 26 × 1 440 texture: one texel is one minute of one day and holds the nearest deploy. That keeps a notch straight at any zoom.
The frame is deterministic and is drawn only when something changes: no random rays, no noise, no battery spent for nothing.
The first frame is the same slice as SVG from the build, which is also the fallback without a GPU and on data saver. The same rings and touches work there.

What is painted and what is measured

From the log: the date, the time to the minute, the number of deploys, the project, the commit, the gate readings and the number of live address errors.
Painted: the wood, the bark, the crack, the unevenness of the trunk. A formula sets the ring thickness, and it grows more slowly than the count.
Times are in UTC, as the log records them. The text of the errors is not in this snapshot, only their number.
Log snapshot: commit 5317d9b, last entry 4 November. Newer deploys, including this site, are not here.

See the sites off this pipeline