-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
publishChecks - how to publish a fail status? #70
Comments
Take a look at https://ci.jenkins.io/pipeline-syntax/ and select You can use the
|
Thanks for the guidance, I'm fairly new to jenkins and its plugins. Thanks for sharing the pipeline-syntax, a valuable tool indeed. I've updated the code to include status and summary. This is my observation, not sure if its an issue.
Thanks for answering my question, I will close this issue as its giving me what I was mainly looking for ie. red cross on fail. yellow dot for in_progress is a good to have. |
PublishChecksStep seems to use ChecksConclusion.SUCCESS by default. Does it work better if you explicitly specify checks-api-plugin/src/main/java/io/jenkins/plugins/checks/steps/PublishChecksStep.java Lines 32 to 33 in 038c259
checks-api-plugin/src/main/java/io/jenkins/plugins/checks/api/ChecksDetails.java Lines 141 to 144 in 038c259
https://docs.github.com/en/rest/reference/checks#create-a-check-run--parameters |
Thanks, explicitly specifying conclusion: 'NONE' did resolve the issue. Thanks again. |
@KalleOlaviNiemitalo thanks very much, the GitHub will automatically set the status to be completed if the conclusion is provided, so maybe I should change the conclusion to NONE when the status is queued or in_progress. |
Help wanted!
Great plugin, we use this in our pipeline. Is there a way to publish yellow dot (in progress) and red cross (fail) when using publishChecks? Below is the syntax we use, and all checks published have a green tick (screenshot for reference)
Syntax:
publishChecks(name: 'Jenkins/SBXDEPLOY Deploy', title: 'Cleanup - IN-PROGRESS', summary: '', text: '', detailsURL: "${JENKINS_URL}")
The text was updated successfully, but these errors were encountered: