Present information around pipeline performance in GitLab CI
## Problem to solve
Currently there is no way for users to understand degradation of pipeline performance (wall clock time of total pipeline or sum of individual jobs or stages) or potential optimization points in a running pipeline without constant vigilance. Users expect some sort of metrics to guide their further steps.
### Primary JTBD
[Debugging a pipeline](https://about.gitlab.com/handbook/engineering/development/ops/verify/pipeline-execution/jtbd/#)
### Intended users
* [Delaney (Development Team Lead)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#delaney-development-team-lead)
* [Sasha (Software Developer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#sasha-software-developer)
* [Priyanka (Platform Engineer)](https://about.gitlab.com/handbook/product/personas/#priyanka-platform-engineer)
## User experience goal
* Users should be able to see in one place how the wall clock time of a project's pipeline(s) are trending over time.
* By providing information on the potential bottlenecks and area of waste in the pipelines, these metrics/data could play a big role in allowing them to optimize and reduce inefficiency.
<!-- How are we going to solve the problem? Try to include the user journey! https://about.gitlab.com/handbook/journeys/#user-journey -->
### Links / references
[Actionable: Prioritization](https://dovetailapp.com/projects/4a4421a9-9fb4-4e16-acab-9ba9042e741d/insights/present/e13e4dc5-6788-4218-8ffa-007581885220)
## Design Proposal
| Insight | Iteration | Comments |
|-------|---------|--------|
| [Actionable: Prioritization](https://dovetailapp.com/projects/4a4421a9-9fb4-4e16-acab-9ba9042e741d/insights/present/e13e4dc5-6788-4218-8ffa-007581885220) | [Pipeline performance insight on detail page - experiment](https://gitlab.com/gitlab-org/gitlab/-/issues/363512) | We ran an experiment by providing this data on the pipeline detail page and [soliciting Feedback](https://gitlab.com/gitlab-org/gitlab/-/issues/365902) from our users over an issue |
|[Users need the flexibility to draw your own conclusions with the presented data](https://gitlab.dovetailapp.com/projects/4ViMk4kyxByXaYOLAigd2X/v/5DHpnVFNmPkZaJXf0ihjeJ/present/5MCZiiXOa2Os6IHueAAU75) + This feature help in comparing pipeline(a sub-job) and it would be helpful to have it at a higher level/more visible | [Improve the presentation of pipeline performance insights](https://gitlab.com/gitlab-org/gitlab/-/issues/381709) | |
| [Wait time on runner helps determine the reason for slowness of a build](uhttps://gitlab.dovetailapp.com/projects/4ViMk4kyxByXaYOLAigd2X/v/5DHpnVFNmPkZaJXf0ihjeJ/present/3yYpKRuo9sEXF8np9ZRvM5) | [Add runner information to pipeline performance](https://gitlab.com/gitlab-org/gitlab/-/issues/381880) | |
| [Contextualize performance information](https://gitlab.dovetailapp.com/projects/4ViMk4kyxByXaYOLAigd2X/v/5DHpnVFNmPkZaJXf0ihjeJ/present/6TCWk6rxYKSg6R4bhNwJj9) | [Contextualize pipeline performance](https://gitlab.com/gitlab-org/gitlab/-/issues/381881) | |
## Implementation Proposal
1. ~"GitLab Free" - Show users basic pipeline duration information https://gitlab.com/gitlab-org/gitlab/-/issues/30989+
1. ~"GitLab Ultimate" - Show users advanced pipeline duration information
- https://gitlab.com/gitlab-org/gitlab/-/issues/357528+
- May include additional features like ability to compare branches, data over longer time frames, job details pulled forward, etc.
1. ~"GitLab Ultimate" - https://gitlab.com/gitlab-org/gitlab/-/issues/352574+
<!-- Label reminders - you should have one of each of the following labels.
Read the descriptions on https://gitlab.com/gitlab-org/gitlab/-/labels to find the correct ones -->
epic