Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

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

Tags:

jenkins

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
like image 295
Amedee Van Gasse Avatar asked Apr 19 '21 13:04

Amedee Van Gasse


People also ask

How do I check if a publisher is enabled or not?

Use the pkg publisher publisher command to view more information about the publisher, such as key, certificate, and proxy. If any origin URI of any of your enabled publishers is unreachable, the install or update operation fails, even if the locations you need are reachable.

What to do if a package is not available from publisher?

If a needed package is not available from a configured publisher but is available from another repository origin, take one of the following actions: Use the -g option of the pkg set-publisher command to add this origin for the solaris publisher.

What happened to the old warnings static analysis plugins?

In order to simplify the user experience and the development process, these plugins and the core functionality have been merged into the Warnings Next Generation plugin. These old static analysis plugins are not required anymore and are now end-of-life.

How to filter the issues shown?

Filtering, Searching: you can filter the shown issues by entering some text in the search box. Content Aware: columns are only shown if there is something useful to display. I.e., if a tool does not report an issues category, then the category will be automatically hidden. Responsive: the layout should adapt to the actual screen threshold.


1 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:

  • JUnit README: https://github.com/jenkinsci/junit-plugin/blob/master/README.md
  • https://github.com/jenkinsci/checks-api-plugin/issues/38
like image 117
user16792896 Avatar answered Dec 31 '22 19:12

user16792896