An overview of ways to log from Jenkin to GitHub Pull Requests as Checks

Hi all,

First time posting here. I wrote a overview recently on the various methods by which you can log stuff from a Jenkins Job to a GitHub PR as “Checks”.

I felt that it might help people decide which way to go, so I wanted to share the link here:

I hope that’s not too spammy and meets the bar of quality here. Thank you.


Hello @tslmy and welcome to this community. :wave:

Thank you so much for your contribution; we truly appreciate it. Have you considered mirroring this effort by publishing your work on the official Jenkins blog ( If you need assistance with that, I’m more than willing to help you get started.

Hi @poddingue ,

Yes, that would be an honor! Please let me know how I can help with the process.

1 Like

Our blog posts are composed in Asciidoc, and we utilize the pull request mechanism to suggest a blog post. This document serves as a guide to help you get started: CONTRIBUTING.adoc.

Should you encounter any challenges in the process, whether it’s related to the Asciidoc format (format-converting tools exist), creating the pull request, or any other aspect, please inform me.
I’m here to assist you. We can continue the discussion in this thread, or if you prefer, we can switch to private messages or email.

Thank you very much. I’ve drafted a PR for that.

The only part I wasn’t able to get through is rendering images locally with make run. When I visit the URL for the image, it says 404, but I’m quite sure I’ve followed the file path convention in this repo. Please let me know if I’ve missed something.

Wow, you’ve already submitted a PR for that—congratulations!
I’ll take a look at the issue you’re encountering with the image.
Thanks a lot!

1 Like