Update usage_overview component
What does this MR do and why?
Relates to #370020 (closed)
In order to enable the pipelines tab vue app (#360785 (closed)) we need to get the app back to feature parity with the current haml view. This is the first of a series of MRs that aims to do that
| MR | Description |
|---|---|
| !95253 (merged) | ( |
| !95256 (merged) | Updates Usage Graphs |
| !95259 (merged) | Updates Project List |
Screenshots or screen recordings
| FF on | FF off |
|---|---|
![]() |
![]() |
How to set up and validate locally
- Make sure to enable:
::Gitlab::CurrentSettings.update(check_namespace_plan: true) - Make sure you're simulating SaaS
- Enable the FF:
Feature.enable(:usage_quotas_pipelines_vue) - Go to any group's usage quotas page
- Check the usage overview
- Turn off FF:
Feature.disable(:usage_quotas_pipelines_vue) - Compare the usage overview
- To add some data:
- Add this to your GitLab settings:
::Gitlab::CurrentSettings.update(shared_runners_minutes: 400) - Project:
project_usage = Ci::Minutes::ProjectMonthlyUsage.find_or_create_current(project_id: project) Ci::Minutes::ProjectMonthlyUsage.update_counters(project_usage, amount_used: 100, shared_runners_duration: 100) - Namespace:
namespace_usage = Ci::Minutes::NamespaceMonthlyUsage.find_or_create_current(namespace_id: root_namespace) Ci::Minutes::NamespaceMonthlyUsage.update_counters(namespace_usage, amount_used: 100, shared_runners_duration: 100)
- Add this to your GitLab settings:
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Edited by Sheldon Led

