We have a Jenkins service connected to a self-hosted Github Enterprise server, and are using Jenkins Pipeline to orchestrate builds. For basic build operations like pushes, commits and PR builds, the functionality is working as expected. When a new PR gets created, the build status appears in the Github PRs with the correct build state generated by Jenkins.

Recently we've started exploring the use of Github Merge Queues so we can streamline our development processes. Most of this feature works just fine with the default options, except for one part: the Jenkins build status. Based on our review, adding a Github PR to a merge queue correctly orchestrates / triggers a Jenkins build (which appears as a PR build using a temporary branch created by Github, as per the described behavior), and the item in the merge queue correctly reports that a build has been triggered. The problem is that the Jenkins build never seems to send back the status information for the build so the queue builder can proceed. This results in the item waiting indefinitely (or until the operation times out), effectively making the merge queue functionality useless.

There is little to no information on the Github docs explaining how to set up third party CI/CD tools with the merge queue feature, however it does mention that this should be supported out of the box. My guess is there is some unique functionality required on the Jenkins side to send build status information back to Github in a format that is slightly different from a typical PR, and as such the information doesn't get detected / reported properly by Github.

It would be amazing if you could look into this and see if there is a simple fix for this on the Jenkins side.