Use last known coverage value for jobs on Group Code Coverage page
Summary
The Daily value for "coverage" on the Group Code Coverage is only using coverage values from jobs that ran that day which leads to swings in the graph not a view of the overall coverage of projects in a group.
Steps to reproduce
- Go to the Gitlab.org group's Repository Analytics page
- View the graph / see data below for 2021-05-12 through 2021-05-14.
What is the current bug behavior?
Each day's value on the graph is only made up of the jobs ran that day, not the last known value of a project's job. This leads to swings in the value of the graph, in the data above the value on the 13th is 36.8% and the value on the 14th is 73.2%.
What is the expected correct behavior?
The overall average should be the last successful job ran.
Relevant logs and/or screenshots
Output of checks
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)