Build Time Regression Doctor

A slower build is easy to notice and hard to explain. Build Time Regression Doctor records each player build, compares it with a healthy baseline, shows where the extra seconds went, and ranks the project changes most likely to explain the regression.

What it helps you do

• Break build time down by Unity build stage and recorded callback.
• Capture Editor log evidence such as shader compilation signals that BuildReport does not contain.
• Compare a slow build with a committed or local healthy baseline.
• Rank changed assets, packages, settings, cache state, and source revisions against measured time deltas.
• Set absolute and regression budgets for local review or CI.
• Run an optional Git bisect in a clean temporary worktree to find the first measured-slow revision.
• Export JSON, Markdown, self-contained HTML, JUnit, and SARIF reports.

Use it when build duration jumps after a merge, a cache change makes CI unpredictable, or a team needs evidence before spending hours on build optimization.

The tool reports what Unity exposes and keeps unclassified time visible. Correlation is ranked evidence, not proof that a changed file caused the slowdown, and noisy machines still need controlled baselines.

Read the complete documentation.