Work out ci pipeline duration instantly with clear inputs, formula shown and shareable results.
Pipeline duration is the sum of its serial stages, and the stage taking the largest share is where optimisation pays. The ten-minute figure matters because beyond it developers stop waiting and switch context, which turns a fast fix into a next-day fix. Caching dependencies, parallelising tests and splitting deploy out of the merge-blocking path are the usual levers.
Pipeline duration
total = checkout + build + test + deploy; bottleneck share = largest stage / total
It is roughly the limit of a developer's willingness to wait. Continuous delivery guidance treats the commit stage as needing to complete inside ten minutes to keep the feedback loop tight.
Only the packaging step. Deploying to production is usually a separate pipeline so pull requests are not gated on environment availability.