[
https://issues.apache.org/jira/browse/HBASE-26788?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17500192#comment-17500192
]
Nick Dimiduk commented on HBASE-26788:
--------------------------------------
This step is coming from [our
use|https://github.com/apache/hbase/blob/ccd908f2187379853093dbb6fd3aabb648343a85/dev-support/Jenkinsfile_GitHub#L253]
of the {{junit}} plugin to "Archive JUnit-formatted test results". The [junit
plugin|https://www.jenkins.io/doc/pipeline/steps/junit/] seems to have support
for [Checks API plugin|https://plugins.jenkins.io/checks-api/], the mechanism
by which Jenkins can publish actions results to Github. I guess we have not
configured something about the Checks API plugin at the stage where the junit
plugin runs, and thus we get this warning. Let me try disabling check
publication at the {{junit}} configuration.
> Fix or disable Checks API callback in builds
> --------------------------------------------
>
> Key: HBASE-26788
> URL: https://issues.apache.org/jira/browse/HBASE-26788
> Project: HBase
> Issue Type: Task
> Components: build
> Reporter: Nick Dimiduk
> Priority: Major
>
> Often as not, PR builds will succeed but be reported on the PR as a failure.
> The reason is represented in Jenkins pipeline as a warning in the "Archive
> Junit-formatted test results", with the message
> {noformat}
> [2022-03-01T22:05:49.166Z] Recording test results
> [2022-03-01T22:05:50.627Z] [Checks API] No suitable checks publisher found.
> {noformat}
> This is confusing and discouraging to contributors.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
