Menu

How we cut ntilde's CI time by 60%
πŸ“°

How we cut ntilde's CI time by 60%

DEV Community: dotnetΒ·Behnam ShomaliΒ·17 days ago
#dRCM6Pjs
#devtodotnet#devto#dev#build#test
Reading 0:00
15s threshold

A typical CI run for ntilde, a cross-platform terminal emulator, went from about 18.7 minutes to about 7 minutes over eight pull requests merged in one day. Every test still runs: each step was checked against the test counts of the run before it, on Windows and Linux. None of the changes was clever. Each one came from reading step timings, finding the next thing on the critical path, and asking why it was there.

CI time after each change

ntilde CI wall time per merged change, 1 November 2026. The start and #682–#704 are typical runs; #707–#717 are single measured runs (9m34s, 8m57s, 8m34s, 7m11s). Runs vary by 10–20 s.

Two changes did most of the work: caching the Rust libraries and sharding the tests. The others saved between 0.4 and 1.4 minutes each, and several of them removed whole kinds of setup from the test jobs, which keeps the next shard cheap to add.

The last two steps need one note.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.