publish code coverage on release build #578
Merged
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
not for anything but internal use, it's not super useful as a metric. but good as an indicator for maintainers.
6 tasks
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.
Tried the tarpaulin action for a simple code coverage, effectively running
cargo tarpaulin --all.Results at https://coveralls.io/github/clux/kube-rs
.
Obviously a bit low because it's not counting actually running the examples (which requires a cluster). Maybe there's a better way to do that.
I have only used coveralls before, so there may be better solutions. This is OK, not amazing for rust, but you can browse around and see. Possibly codecov.io is better.
Run took about 7minutes, only wanted this as a quick thing to look at every now and then so didn't bother with caching:
https://github.com/clux/kube-rs/runs/2985127374?check_suite_focus=true
figured for now, once per release is better than nothing, don't really feel like we need the whole "your code coverage decreased" notifications on prs, but it's nice to have an lcov browser.
also bundled in with this is a clippy change