Aggregated coverage report without using codecov #2975
+2
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAll modified and coverable lines are covered by tests ✅ Additional details and impacted files@@ Coverage Diff @@
## develop #2975 +/- ##
=============================================
+ Coverage 56.85% 58.54% +1.70%
+ Complexity 9800 127 -9673
=============================================
Files 2281 2377 +96
Lines 97624 102404 +4780
Branches 7208 7737 +529
=============================================
+ Hits 55491 59945 +4454
- Misses 40047 40201 +154
- Partials 2086 2258 +172 |
da-Kai
approved these changes
Jan 21, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this MR do?
It adds a new Gradle Plugin named JacocoLog. This plugin prints the instruction coverage to stdout.
Why is this MR needed?
We have a GitLab Pipeline without using codecov Bot. GitLab is able to directly consume the code coverage from the stdout of the build job. As we think this feature is useful for others, we wanted to share this contribution. It also mitigates an eventual future merge conflict in out fork.