Buildline unifies Cargo and Ninja logs into one build timeline

Buildline set out to answer a simple build-time question: what new optimization decisions become possible when you can see one merged timeline? The tool pulls Cargo timing data and Ninja logs into a single view, which matters when the real bottleneck is the gap between build tools, not the compiler itself. In one launch example, the gap was 2.7 seconds between Ninja finishing and Cargo starting.

That focus on inter-tool visibility is the whole pitch. Cargo already gives developers a timing report through `cargo build timings`, and The Cargo Book says it records how long each compilation takes while tracking concurrency over time. The report lands at `target/cargo-timings/cargo-timing.html`, with a timestamped copy saved in the same directory. Buildline does not replace that output; it layers on top of it so the Cargo view can be lined up with Ninja’s log stream.

That distinction matters in mixed-language builds, especially in Rust projects that still rely on native code generation, linking, or other steps outside Cargo. Ninja’s manual describes it as a small build system built for speed and designed to be driven by a higher-level build system, which is exactly why it shows up beside Cargo in larger pipelines. When each tool reports only on its own slice of the build, dead time between them can disappear from view.

The Buildline package is listed on docs.rs as version 0.1.0, and its README tagline says, “One timeline for your whole build.” The same theme runs through the announcement thread on The Rust Programming Language Forum and a matching DEV Community writeup, both of which frame Buildline as an observability layer over an existing workflow rather than a new build system to adopt.

Cargo’s own timing output has already helped people spot odd behavior. In one Rust forum discussion about `cargo timings`, a developer trying to verify absurdly long compilation times said the same `image` crate version appeared to be compiled multiple times. Buildline pushes that idea further by lining up the Cargo report with Ninja logs, so the question stops being whether a crate compiled slowly and becomes where the build actually stalled.

For teams trying to shave time off CI without guessing, that merged timeline is the point. It turns separate logs into one sequence, which makes bottlenecks easier to pin on compilation, code generation, linking, or the quiet pauses between them.