Jenkins github pull-builder plugin doesn't send to github

Question

I configured the Jenkins Github Pull-Request plugin to create each pull request made by members of my institution. It works great.

However, the assembly does not report the status of the assembly on github, as shown in this nice post. I also tried to check the box "Use comments to report results when updating commit status", but I still do not return anything to github.

I created a bot user on GitHub and gave him push and administrative repo rights.

My Jenkins server is behind a firewall, but since it works fine and detects changes (by polling) in the github repository, I assume this is not a problem.

Has anyone else had this problem? How did you solve it?

Here is a dump of my console output (compressed for readability)

Started by an SCM change Building in workspace Fetching changes from the remote Git repository Fetching upstream changes from repo Seen branch in repository origin/HEAD Seen branch in repository origin/master Seen branch in repository origin/pr/1/head Seen branch in repository origin/pr/1/merge Seen branch in repository origin/pr/10/head […] Seen branch in repository origin/pr/9/head Seen branch in repository origin/pr/9/merge Seen 33 remote branches Checking out Revision 9b4d45ee3a2d265a1268c2931e7b2bcb738e1c87 (origin/pr/16/merge) First time build. Skipping changelog. ...found 160 targets... ...updating 21 targets... **passed** test/bin/test.test/gcc-4.8.1/debug/test.test [xUnit] [INFO] - Starting to record. [xUnit] [INFO] - Processing BoostTest-1.x (default) [xUnit] [INFO] - Check 'Failed Tests' threshold. [xUnit] [INFO] - Check 'Skipped Tests' threshold. [xUnit] [INFO] - Setting the build status to SUCCESS [xUnit] [INFO] - Stopping recording. Finished: SUCCESS 

Answer 1

Looking at Jenkins LOGS, I learned a few things:

• This plugin (github pull-request builder) completely replaces all other assembly triggers (including git and SCM polling). I used all three, and when I thought this plugin works because it builds correctly, there were actually other triggers.
• You must set the github project url in the github plugin. This plugin depends on the github plugin to work. This is what prevented him from working in my configuration.

After fix number 2, you can remove the triggers from the SCM and git polls to make sure the pull-request plugin starts the build. When he does this, he actually adds the transfer request link to the activity feed in Jenkins (very good) and correctly updates the state of github.