Hi Dj, I think there could be either one of these 2 issues:

Create a new PR (or comment ‘rerun’ to the already created PR — if you already set up the trigger with the string ‘rerun’), check to see if the build runs in Jenkins.

1. If it does, then check your GitHub settings under WebHooks to see if there is a webhook set up with the payload url set to http://your-jenkins-server.com/ghprbhook/ and is active. This should be automatically set up by the github-pr plugin mentioned above. If not, you could try to manually set it up, but I would try to set up the plugin again so that it’s automatically set up. If you choose to set up manually, then make sure the payload set to the above mentioned url, content-type to www-form-urlencoded, and for events, select: Issue Comments and Pull Requests. Another possible issue is that you might not have the correct GitHub credential or a correct admin in the “admin list” under Build Triggers.
2. If your build won’t run, in your Jenkins build config, under Source Code Management, try changing the config for refspec to
   
   +refs/pull/${ghprbPullId}/*:refs/remotes/origin/pr/${ghprbPullId}/*
   
   instead of +refs/pull/*:refs/remotes/origin/pr/*

• Like in #1 above, make sure under Build Triggers, you have the correct Github credential and correct admins inside the “admin list”

It’s hard to help debug it remotely, but I hope these steps can give you some ideas where to track where the issue is. Let me know!