How to get rid of noisy warning "No suitable checks publisher found"

user_766786 0
Viewed 7841

One of the Jenkins plugins dragged in the Checks API as a dependency and now EVERY build has this annoying message at the bottom:

[Checks API] No suitable checks publisher found.

This does not fail any build by itself. It's just annoying noise and I don't want it.

And now each time a build fails for any other reason, my developers tell me

It seems that we have problems with build on foobar machine with 'No suitable checks publisher found' error again.

which is incorrect, the actual error is just above or below that warning.

This is a waste of time, I never want to see that warning again. How do I get rid of it?

I can't uninstall Checks API, it's grayed out. JUnit and Warnings Next Generation need it as a dependency.

  • Jenkins: 2.277.2
  • Checks API: 1.7.0
jenkins
2 Answers

You can disable the check feature by:

junit testResults: 'results.xml', skipPublishingChecks: true

Check the README.md of JUnit plugin for more details:

Test result checks (for GitHub projects)
⚠️ This feature requires:

the installation of an additional plugin: GitHub Checks Plugin
the configuration of GitHub App credentails, see this guide for more details.
If not disabled in the job configuration, this plugin will publish test results to GitHub through GitHub checks API.

In the Details view of each check (example), test results will be displayed.

checks

In order to disable the checks feature, set the property skipPublishingChecks to true:

References:

user_167928960

With the following action in my Jenkinsfile...

    post {
        always {
            junit testResults: '**/cpputest_*.xml'
        }
    }

I get the

[Checks API] No suitable checks publisher found.

warning as described in the original question.

Adding the "skipPublishingChecks" option as described in the junit plugin's readme file...

    post {
        always {
            junit skipPublishingChecks: true, testResults: '**/cpputest_*.xml'
        }
    }

...results in the warning no longer being shown. In my case (vanilla Jenkins 2.365), and contrary to a comment by @rveach above, the test result trend is still shown (and updated) on the job's 'Stage view' page.

user_104737030
Related