Citooling: find where your CI pipeline loses time
Paste GitHub Actions job timings. See where the wait goes and what to fix first.
step name 1m 05s under job nameJSON: gh api repos/OWNER/REPO/actions/runs/RUN_ID/jobs- 1Undersized runnerbuild-and-test: 10m 24s build + test (70%) on ubuntu-latest10m 24sBuild, Test
- 2Serial testsbuild-and-test: 7m 46s in one test step (52% of the job)7m 46sTest
- 3Slow installsbuild-and-test: 1m 54s installing1m 54sInstall
- 4Cold cachesbuild-and-test: 1m 34s in cache steps (11%)1m 34sCache restore
How the analysis works
Three passes over your timings, all in the page. Every threshold is on the method page.
Paste
A run export from the GitHub API, or step lines copied from the job page.
Classify
Each step goes to a phase by its name. Queue comes from timestamps.
Rank
Rules flag bottlenecks. Time in the affected phases sets the order.
Worked examples
Illustrative timings, written to show each rule firing. Load one to see the full result.
One job runs every test
Caches that restore cold
A run export with a long queue
Questions people ask
Short answers. The method has the long ones.
What is Citooling?
A free CI tooling analyzer. Paste GitHub Actions job timings and it shows the time in each phase (queue, setup, cache, install, build, test) and which fix to make first. No sign-up.
Is anything I paste uploaded?
No. The analysis runs in your browser. A share link carries the timings after the # in the URL, a part browsers never send to a server.
How do I get my workflow run timings?
Run gh api repos/OWNER/REPO/actions/runs/RUN_ID/jobs and paste the JSON. Or copy step durations from the job page as one “name duration” line each.
Why does my breakdown show no queue time?
Step lists from the job page don't include it. Add a line such as “Queued 41s”, or paste the API JSON, where queue time is started_at minus created_at.
Will a faster runner change my test results?
It shouldn't: the same steps run. Check it: run one commit on both, and the conclusion and test count must match. Each fix page lists its checks.
Is “time at stake” a promised saving?
No. It is the time your pasted run spent in the phases a fix addresses, for that workload only. Measure the change with the baseline compare.
Which runner should I use for a runner-bound job?
Graphide CI moves x64 Linux jobs with a one-line runs-on change, on warm machines sized to each job. The runners page sets it beside GitHub-hosted, self-hosted and other services on the same criteria.