[
https://issues.apache.org/jira/browse/NIFI-12192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Sampson updated NIFI-12192:
---------------------------------
Description:
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 - https://github.com/marketplace/actions/jacoco-report
was:
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.
> 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
> Priority: Minor
> Fix For: 2.latest
>
>
> 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 - https://github.com/marketplace/actions/jacoco-report
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
