Skip to content

Frontend: Provide visibility for shared runner usage for user namespaces

Release Notes

Tracking how many of your CI Minutes you are using each month for public projects is hard, especially across projects.

Now each namespace's CI Minute usage is displayed along side the Runner Duration in the Usage Quota. You can see how many minutes each project has used by month and how minute usage is trending overtime.

Problem to solve

In #340504 (closed) we are adding a section under Analytics>>CI/CD at group level to expose shared runner usage. We should treat top-level groups and user namespaces the same with regards to this data. But user namespaces don't have Analytics section.

User experience goal

Users should be able to get access to the shared runner usage for the projects under the namespace.

Proposal

Scope of this issue:

  1. Change text for existing CI Minutes usage to CI/CD minutes everywhere on usage quota page
  2. Add a padding under Pipelines tab and and change header font size
  3. Introduce Shared runners usage tab with popover for Monthly usage charts only

Not in scope of this issue

  1. Introduce Shared runners usage tab with popover for By project charts only
  2. Add shared runner duration consumption information to the table below

We accumulate shared runners duration at root-namespace level but we also have the usage per project. We should be able to display the equivalent chart as User Settings > Usage Quotas > CI minutes usage by project.

Availability & Testing

Ensure we have feature tests for this page.

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

  • User is able to access the shared runners duration analytics for their personal namespace.
  • This Analytics page (like Usage Quotas page) is only available to the namespace owner.
  • This new page is documented for User Namespaces and Groups in https://docs.gitlab.com/ee/ci/pipelines/cicd_minutes.html

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.

Edited by Mark Nuzzo