-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Add report_type column to commit reports #287
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #287 +/- ##
=======================================
Coverage 95.64% 95.65%
=======================================
Files 610 612 +2
Lines 15714 15734 +20
=======================================
+ Hits 15030 15050 +20
Misses 684 684
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #287 +/- ##
=======================================
+ Coverage 95.55 95.56 +0.01
=======================================
Files 724 726 +2
Lines 16121 16141 +20
=======================================
+ Hits 15404 15424 +20
Misses 717 717
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM thank you!
- Perhaps its better to have a
report_type
type as enum for this new column in the DB. - Is the
report_uploads
table currently fully compatible to support any type of reports?
Yeah I suppose this will change so infrequently that it makes sense to encode this at the db level. Though I'm only seeing
I think so - they're all very generic columns in the uploads table and are related more to a CI environment than anything Codecov specific. One thing to keep in mind is that it won't make sense to query for all uploads on a commit just by joining commitreport naively - there should always be a condition on the |
Codecov Report
@@ Coverage Diff @@
## main #287 +/- ##
=======================================
Coverage 95.64% 95.65%
=======================================
Files 610 612 +2
Lines 15714 15734 +20
=======================================
+ Hits 15030 15050 +20
Misses 684 684
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Purpose/Motivation
To support test results and bundle analysis ingestion. This will allow us to reuse the
reports_upload
table for new types of ingest and process those uploads intoreports_commitreport
records for other types of per-commit reports.Here's some initial work on how
worker
will handle this: codecov/worker#190Links to relevant tickets
N/A
What does this PR do?
Adds a new
report_type
column toreports_commitreport
. Existing rows will be null and null will be interpreted to mean "coverage" reports. Valid values for this column are "coverage", "test_results" and "bundle_analysis".Existing queries for commit reports were updated to include only "coverage" reports. They can be updated in the future as needed to handle switching between the various report types.