CI Analytics: Group View for CI Pipeline Metrics

Problem(s) to solve

Missing Pipeline Performance Analytics - GitLab admins and DevOps teams cannot easily track pipeline performance across multiple projects over time, making it difficult to proactively identify performance degradation before it impacts developers.

The fundamental problem is that GitLab's current CI pipeline monitoring capabilities are project-siloed and lack the analytical depth needed for enterprise-scale CI/CD operations, particularly around reliability detection and cross-project performance insights.

JTBD: As a GitLab Admin/DevOps Developer, I want to see performance (how fast they finish) of pipelines in many projects over time, so I can identify which are slowing down and fix them before developers complain i'm not doing my job.

Intended users

Proposal - TBD

Next Steps

• Validate which metrics this persona needs at this level and over what time frame they care about
• Explore providing group level CI/CD insights to Gitlab CI users by exposing critical analytics under Group>>Analytics>>CI/CD.

Further details

Permissions and Security

Available Tier

• Ultimate

Feature Usage Metrics

For whatever the view is we would track views on that page and clicks into the next level if/when provided.

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.

📝 Background

From the UX scorecard research gitlab-design#1671 (closed) we learned that there is not group level summary for pipeline performance available today.