[
https://issues.apache.org/jira/browse/CURATOR-660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17700453#comment-17700453
]
Zili Chen commented on CURATOR-660:
-----------------------------------
Reopen the ticket and retract the comment "codecov doesn’t work well in OSS
projects".
-1 because:
Different from checkstyle or license header checker, contributors hardly review
the codecov report and also the “test coverage” is seldom correct (Experiencing
many times I change a comment and codecov complains that the test coverage is
lowered, I don’t think it’s a good experience for the following contributors).
However, as it’s not integrated into automation, it won’t complain following
PRs also.
Here are my previous comments on codecov alike tools:
https://lists.apache.org/thread/806ktn2h5q9omogv2t9j28mcvnttkqqr.
I also reject other patchs that do no harm but do no benefit, like
https://github.com/apache/curator/pull/418.
Metrics, reports, ..., only if the contributors or reviewers take it into
account, it can help. If other Curator contributors support that they need such
a script, we can give it a try.
> Enable code coverage reporting to SonarQube
> -------------------------------------------
>
> Key: CURATOR-660
> URL: https://issues.apache.org/jira/browse/CURATOR-660
> Project: Apache Curator
> Issue Type: Task
> Reporter: Dóra Horváth
> Assignee: Zili Chen
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Enable coverage report generation and publishing to SonarQube.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
