Pipeline timing graphs
Understand the speed of your CI/CD pipelines is tough and we should make it easier. One step in that direction is providing historic graphs of pipeline timings. Perhaps as simple as the overall time for the
master pipeline; perhaps timing broken down by stage or even job; perhaps information for other branches (especially for testing pipeline improvements in a branch before merging to master). Since jobs run in parallel, you can't just show the sum of all jobs, but you could identify which job was the slowest for each stage, and somehow make it easy to see if there's a certain job that is consistently the bottlenck.
Links / references
(Write the start of the documentation of this feature here, include:
- Why should someone use it; what's the underlying problem.
- What is the solution.
- How does someone use this
During implementation, this can then be copied and used as a starter for the documentation.)