Historical pipeline timing graphs
Description
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.
Proposal
Links / references
Documentation blurb
(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.)
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.