Director-level CI/CD Group Dashboard
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.
Problem to solve
As an extension of #3277, we could consider a CI/CD MVC to address
During the user interviews, the majority of pain points expressed by users related to their managers and their inability to track project status at a high level within GitLab's interface. If management isn't happy with GitLab, then it slows down the adoption of GitLab within a company and there's a potential for that to have an impact on purchasing licenses, upgrading, ditching legacy tools, etc.
Intended users
- Rachel (Release Manager)
- Buyers/ Directors
- Delaney (Development Team Lead)
Further details
Create a single view of the most important, relevant group level metrics. We would want to consider and evaluate the top 8 that users would find the most relevant. Considerations would be:
- Any performance metrics
- time comparison views at the group level
Proposal
- In the "Group Overview" section, include a menu option to
CI/CD Dashboard
- The CI/CD Dashboard should display tiles that aggregate all of the project data into the following metrics:
- Releases:
- Releases insights (all time): Total count of releases in a group, total count of upcoming releases, percentage of project with releases.
- Last 5 updated releases: a list of the last 5 updated releases in projects that belong to the group. Display project name (link), release title (link), and status (upcoming, released).
- Historical vs. Upcoming releases: a bar graph with the comparative data for historical vs. upcoming releases in the last year (NB: time frame needs to be validated).
- Pipelines:
- Pipeline insights (all time): Total count of pipelines in a group, total percentage of passing releases, total percentage of failed with pipelines.
- Last 5 passed pipelines in group: a list of the last 5 passed pipelines. Display status, ID, triggerer, pipeline detail, pipeline chart with icons, time stamp.
- Last 5 passed failed in group: a list of the last 5 failed pipelines. Display status, ID, triggerer, pipeline detail, pipeline chart with icons, time stamp.
- Releases:
Permissions and Security
- We should consider this a view-only for all users.
Documentation
- Understand the Group documentation and any implications we may have for aggregating this data at that level
Availability & Testing
- We should investigate how real-time this can be in GitLab so that it does not become a performance issue
What does success look like, and how can we measure that?
- Users are viewing the dashboard and clicking into data displayed
- For example: if a user wanted to see a specific environment in the top 5 list they could click a link and navigate to that environment
What is the type of buyer?
- Premium