CI Pipeline Critical Path Visualizer
Find the longest dependency chain in your pipeline. The critical path is the only thing that decides how fast your CI can possibly finish.
Adding more parallel jobs does nothing if your slowest dependency chain is unchanged. This tool takes your jobs, their needs: dependencies and durations, computes the critical path and wall-clock time under unlimited parallelism, and shows where your billed minutes go.
What it computes
- Critical path: the longest chain of dependent jobs, e.g. build → test → deploy = 13 min.
- Wall-clock time assuming unlimited parallelism (the earliest the whole pipeline can finish).
- Total billed minutes (the sum of every job, which is what you actually pay for).
- Parallelism factor = billed / wall-clock, showing how much you gain from running jobs concurrently.
Cycle detection
If your needs: graph contains a cycle (job A needs B and B needs A, directly or transitively), the analysis reports the cycle instead of looping forever. A cyclic dependency graph can never run, so catching it here saves a failed workflow.
Lowering the critical path
To make CI faster, shorten the longest chain: split a slow job, cache its inputs, or remove an unnecessary needs: edge so the job starts earlier. Run the result on Latchkey managed runners to cut per-minute cost on the billed total.