[
https://issues.apache.org/jira/browse/CURATOR-660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17704115#comment-17704115
]
Andor Molnar commented on CURATOR-660:
--------------------------------------
{quote}However, as the patch (PR-442) is not integrated into automation, it
won’t complain following PRs also.
{quote}
That's the point. The patch doesn't touch current Curator builds or Maven
profile and don't want to change your existing workflows. It's an optional
feature which adds a custom maven profile which makes easier for users to
integrate code coverage in their CI flow.
{quote} Metrics, reports, ..., only if the contributors or reviewers take it
into account, it can help.
{quote}
Agreed, but this patch is not about adding any of these.
> 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)
