Use average of coverage values to avoid upsert error
What does this MR do?
Solves #213049 (closed)
In some projects, it's possible that they use grouping for their test builds, and it's possible that each build in the group would store its own coverage value. When gathering
the data to upsert into the ci_daily_report_results table, we use the group_name for code coverage reports. This would cause duplicate instances of the group_name which would then cause an SQL error.
To fix this, I modified it to get the average coverage of each group name. This is consistent with how we do it for pipelines.
Screenshots
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team