Comments (29)
For what it's worth to anyone coming here now, I added skipPublishingChecks: true
to skip this troublesome part. It appears to have been added here (linked PRs in the right column) although i found it first in the plugin's docs.
I know that our Enterprise GitHub is getting build status updates from Jenkins, so those checks are being published some other way, and I was ok to remove this one.
junit testResults: 'results.xml', skipPublishingChecks: true
from checks-api-plugin.
Looks like JUnit plugin has Check API plugin as dependency.
https://plugins.jenkins.io/junit/#dependencies
from checks-api-plugin.
Which plugin are you using? Currently, there are warnings-ng and code-coverage plugins are using the checks-api plugin, and they all provide configurations to skip publishing checks. E.g, for warning-ng plugins: https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md#warnings-checks-for-github-projects
from checks-api-plugin.
Hello.
I do not have any of those 2 plugins. I can provide full list of plugins installed if that would help.
My pipeline is scripted pipeline where I have something like this
stage('SOURCE') {
git credentialsId: 'xxxxx', branch: "some_branch", url:"some_url"
}
After git command I get "[Checks API] No suitable checks publisher found."
After that stage I have stage where I build app using maven but I am not getting that message in that stage. And at the very end I have this (all stages are finished):
[Checks API] No suitable checks publisher found.
Finished: SUCCESS
from checks-api-plugin.
Check if you have installed the checks-api-plugin, just uninstall it.
from checks-api-plugin.
I do have it, but it was installed as dependency for some plugins that I updated (not installed) this morning.
These were updated (or installed as dependency) this morning:
timestamper.jpi
junit.jpi
checks-api.jpi
credentials-binding.jpi
workflow-step-api.jpi
But I can't uninstall it, it is greyed out.
from checks-api-plugin.
junit plug-in started use this API: jenkinsci/junit-plugin#180
from checks-api-plugin.
Yeah I just saw this:
1.39
Released: 2 days ago
🚀 New features and improvements
Checks API integration (#180) @timja
from checks-api-plugin.
This does not only affect console output of pipeline jobs. Every classic freestyle job also has this message in its console output.
from checks-api-plugin.
Hello.
I see that 1.0.3 update is ready, but looks like this change is not there yet?
from checks-api-plugin.
Yes, that's daily dependencies update. This change will be merged soon, only tests are left.
from checks-api-plugin.
We have the same "problem" that junit-plugin prints "[Checks API] No suitable checks publisher found."
We are using version 1.0.3 of checks-api-plugin and it is a dependency of junit-plugin.
Is there some progress on this issue?
How do we get rid of this log output "[Checks API] No suitable checks publisher found." ?
from checks-api-plugin.
Just released: https://github.com/jenkinsci/checks-api-plugin/releases/tag/v1.1.0. This should have solved this problem,
from checks-api-plugin.
I am running version 1.2.0 of the checks-api now, but stil get the messages "[Checks API] No suitable checks publisher found." in the console logs.
Is there any thing else to configure to 'suppress' these messages?
from checks-api-plugin.
I am running version 1.2.0 of the checks-api now, but stil get the messages "[Checks API] No suitable checks publisher found." in the console logs.
Is there any thing else to configure to 'suppress' these messages?
Are you using any consumer plugins of this API (e.g. warnings-ng, junit, or code-coverage)?
from checks-api-plugin.
We have the junit plugin installed, but I am not using this in my jenkins job. This is a 'simple' pipeline job.
The message is shown after a git checkout and at the end of the pipeline job.
from checks-api-plugin.
Isn't our listener independent of any consumer? That means the message will be written out for every job.
from checks-api-plugin.
Isn't our listener independent of any consumer? That means the message will be written out for every job.
it's independent, but if using a consumer plugin like warnings-ng (without implementation), we'll also see that message. I'm just to make sure it comes from the listener.
from checks-api-plugin.
@kad-meedel Does your Jenkins install the github checks plugin? I seem to have found a problem, but not sure if that's your case.
from checks-api-plugin.
We do not have a separate install of the github-checks or the checks-api plugin.
I think one of the other plugins has checks-api plugin as an dependencie! Pipeline: step api fore instance.
from checks-api-plugin.
We do have an installation of the GitHub Branch Source pugin. This one has an dependency with github checks
from checks-api-plugin.
We do have an installation of the GitHub Branch Source pugin. This one has an dependency with github checks
I may need your double-check for it?
our github checks plugin do dependent on github branch source plugin, but not the other way around, see https://github.com/jenkinsci/github-checks-plugin/blob/f9c6e9691269729540b5d94243597a15f89fa05b/pom.xml#L89
from checks-api-plugin.
Yes you are right.
And we do not install the github checks plugin.
So what would than be the trigger?
from checks-api-plugin.
from checks-api-plugin.
The message is shown after a git checkout and at the end of the pipeline job.
According to your description, it looks like something goes wrong with our the status checks feature although we have carefully designed it not to publish status checks when no implementation is installed. But I can't reproduce it: I deleted the github-checks and runs a template pipeline job, nothing related in its log, however.
pipeline {
agent any
stages {
stage('Build') {
steps {
// Get some code from a GitHub repository
git 'https://github.com/jenkins-checks-api-test/codingstyle'
// Run Maven on a Unix agent.
sh "mvn -Dmaven.test.failure.ignore=true clean verify"
}
post {
// If Maven was able to run the tests, even if some of the test
// failed, record the test results and archive the jar file.
success {
archiveArtifacts 'target/*.jar'
}
}
}
}
}
Can you simply replay it or create a job to test it and show me the log? Or can you show me your script (you can filter the sensitive information)?
from checks-api-plugin.
That's not the problem if not installing the github-checks, since no properties implementation exists at all (other than the default one which is not applicable to any jobs):
from checks-api-plugin.
I have run the pipeline script as you mentioned. I only included the mvn tool in the code. ( is not a default implementation )
jenkins-checks-testrun.txt
from checks-api-plugin.
In a 'simple' pipeline job the message is gone. In a 'simple' jenkins project the message is stil there.
from checks-api-plugin.
Check if you have installed the checks-api-plugin, just uninstall it.
how??
from checks-api-plugin.
Related Issues (20)
- Primary error message is not shown in error header, instead says `error in 'error' step` HOT 5
- Do not report handled exceptions HOT 3
- Build log Output truncated. - print tail of log instead of head HOT 2
- Allow using specific credentials for Checks HOT 5
- How do I create a custom rerun check in Pipeline HOT 1
- 1.7.5: download plugin checks-api to file: status code: 403, reason phrase: Forbidden HOT 2
- Phantom release 1.7.5 of checks-api HOT 1
- Possibility Of Specifying Credentials HOT 3
- Fix flaky test `BuildStatusChecksPublisherITest.shouldPublishStageDetails`
- [Question] Hanging checks with "withChecks()" HOT 5
- Include optional checks publisher to warnError HOT 1
- [doc] How to get started? HOT 5
- How to publish checks from sub-jobs HOT 1
- Dependency Dashboard
- Tests fail on Java 21 with Mockito errors HOT 2
- Setting Status checks name does not change it from the default Jenkins HOT 4
- Dependencies of flattened POM of latest release do not match `MANIFEST.MF`
- Return information about the check
- checks not working for Bitbucket scm HOT 1
- Steps with labels are not logged as errors HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from checks-api-plugin.