[
https://issues.apache.org/jira/browse/NIFI-12192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17784189#comment-17784189
]
ASF subversion and git services commented on NIFI-12192:
--------------------------------------------------------
Commit 5554bab51638b5860a0fd28a7522eba89e7bf893 in nifi's branch
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=5554bab516 ]
NIFI-12192 Added Codecov Reporting with JaCoCo
- Added report-code-coverage profile to nifi-assembly for aggregation
- Added Codecov reporting to Ubuntu Linux Job in ci-workflow
- Added Codecov badge to README.md
This closes #7995
Signed-off-by: Chris Sampson <chris.sampso...@gmail.com>
> GitHub Action Workflows could better report Tests Results and Summaries
> -----------------------------------------------------------------------
>
> Key: NIFI-12192
> URL: https://issues.apache.org/jira/browse/NIFI-12192
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Chris Sampson
> Assignee: David Handermann
> Priority: Minor
> Fix For: 2.latest
>
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> Several of the GitHub Action Workflows produce {{JUnit}} XML result output
> files through {{surefire}} and {{failsafe}} plugins. These are currently
> uploaded as raw logs/XML files for people to download from GitHub, but it
> should be possible to upload these results as {{checks}} within GitHub
> instead, which would be easier for people to consume and understand what
> tests are failing in their PRs.
> One possible action to use would be
> [test-reporter|https://github.com/marketplace/actions/test-reporter],
> although an attempt to use this in NIFI-12177 as part of the new
> {{integration-tests}} Workflow failed because it seems we're unable to
> {{write}} to the GitHub repo (even with {code:yaml}permissions.checks:
> write{code} set within the Workflow definition). This might be an intentional
> setting, and could require discussion with the ASF Infrastructure team to
> understand whether this is/could be permitted.
> Also consider adding test coverage reporting, at least for one of the
> ci-integration jobs, see tools such as:
> * https://github.com/marketplace/actions/jacoco-report
> * https://github.com/codecov/codecov-action (see
> https://github.com/exceptionfactory/jagged for example implementation)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
