Project level CI/CD Analytics not reporting on GitLab.com
Summary
Since this month, project level CI/CD analytics stopped reporting, nothing showing up in the dashboard
Steps to reproduce
- Go to a project where pipelines are run regularly]
- Access to the project's CI/CD analytics view
- Stats in November onward are not displayed
Example Project
https://gitlab.com/gitlab-org/gitlab/-/pipelines/charts
What is the current bug behavior?
Metrics are not shown in the dashboard even though pipelines are run regularly after November
What is the expected correct behavior?
CI/CD analytics should function
Relevant logs and/or screenshots
Output of checks
This bug happens on gitlab.com
Results of GitLab environment info
Expand for output related to GitLab environment info
(For installations with omnibus-gitlab package run and paste the output of: \\\`sudo gitlab-rake gitlab:env:info\\\`) (For installations from source run and paste the output of: \\\`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production\\\`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(For installations with omnibus-gitlab package run and paste the output of: \`sudo gitlab-rake gitlab:check SANITIZE=true\`) (For installations from source run and paste the output of: \`sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true\`) (we will only investigate if the tests are passing)
Possible fixes
Patch release information for backports
If the bug fix needs to be backported in a patch release to a version under the maintenance policy, please follow the steps on the patch release runbook for GitLab engineers.
Refer to the internal "Release Information" dashboard for information about the next patch release, including the targeted versions, expected release date, and current status.
High-severity bug remediation
To remediate high-severity issues requiring an internal release for single-tenant SaaS instances, refer to the internal release process for engineers.