ffpcrm GitHub Actions ·

Seven weeks of CI: what it cost, how fast it was, and what Jog changed

Corrected edition, Oct 19 2026: full run list (28,955 runs) and the full job sample; pass rate excludes skipped and cancelled runs

Before and after the Jog cutover

Warp era is Sep 1 to Oct 14. Jog era is Oct 15 to Oct 18, four full UTC days. Per-day rates, so the short Jog window compares fairly, but four days is an early read.

Daily spend by provider

Estimated list-price dollars per day, stacked by where the jobs actually ran. Hover a day for the split.

The providers

Measured from sampled job records: queue time is job created to job started, and $/min is the effective list price after per-job rounding.

Where the money goes: by repo

Estimated spend for the whole window, stacked by provider. The right column is runs, success rate, and median run time.

By change type

Each run is classified from its head commit: conventional-commit prefix first, Dependabot as dependencies, security keywords (CVE, GHSA, vuln, RLS, secret, injection) as security, and plain-English fallbacks after that.

Spend per repo and change type (darker is more)

Timeliness

How long a pull request waits for its CI verdict, week by week (run created to run finished, completed runs only).

Slowest and costliest workflows

Waste

Spend on runs that produced no verdict, or produced one twice.

Other cool stuff

Same job, different runner: median minutes and cost per successful run
When CI runs (runs started, Central time)
Most expensive pull requests
GitHub's own bill (measured, Actions only)