[Discovery] Pipeline-based metrics

Problem to solve

Every MR which uses CI\CD at Gitlab has one or several pipeline runs. The number of pipeline can be useful to detect problematic MRs and project-wide trend lines.

Intended users

Since it's a proof of concept it's intended for gitlab internal users only.

Further details

Proposal

Add a chart at productivity analytics page which lists 50 MRs with highest number of pipeline runs across given selection. Listing should display following metrics:

• number of pipeline runs
• number of pipeline runs per day as (pipelines count / (MR merge date - MR start date))
• pipelines failure percentage

Permissions and Security

same as regular Productivity Analytics access

Documentation

Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Links / references