Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-42992

Webhooks don't work from GitHub Enterprise when using Multi-Branch Pipeline jobs

      I have followed the documentation to manually setup the webhooks at https://support.cloudbees.com/hc/en-us/articles/224543927-GitHub-webhook-configuration but my multi-branch pipeline jobs never get triggered. I've had to switch to using the standard git plugin to trigger the multi-branch pipeline jobs but that has less functionality than the GitHub branch source plugin (i.e. no pull requests). I haven't had any issues with webhooks from GitHub Enterprise on the standard pipeline jobs, just the multi-branch pipeline jobs. 

          [JENKINS-42992] Webhooks don't work from GitHub Enterprise when using Multi-Branch Pipeline jobs

          Ryan Campbell added a comment -

          Can you please provide the GitHub Enterprise version information? Also, can you please check GHE to see if the hooks were delivered?

          This is generally missing steps to reproduce. For us to be able to see if this is a bug, we need to know the step-by-step description of how to reproduce the issue.

          Ryan Campbell added a comment - Can you please provide the GitHub Enterprise version information? Also, can you please check GHE to see if the hooks were delivered? This is generally missing steps to reproduce. For us to be able to see if this is a bug, we need to know the step-by-step description of how to reproduce the issue.

          Eric Dalling added a comment -

          We are using GHE version 2.8. I tried setting up both Webhooks and the Jenkins (GitHub plugin) Service in GHE but neither approach triggered the multi-branch pipeline jobs even though GHE indicates that the triggers were successfully delivered. The Jenkins 'Repository Events' log doesn't show anything about a hook being received. These same webhooks/services work fine to trigger my standard pipeline jobs in Jenkins.

          Here are some screenshots from the GHE configurations:

          Eric Dalling added a comment - We are using GHE version 2.8. I tried setting up both Webhooks and the Jenkins (GitHub plugin) Service in GHE but neither approach triggered the multi-branch pipeline jobs even though GHE indicates that the triggers were successfully delivered. The Jenkins 'Repository Events' log doesn't show anything about a hook being received. These same webhooks/services work fine to trigger my standard pipeline jobs in Jenkins. Here are some screenshots from the GHE configurations:

          Tim Jacomb added a comment -

          Try taking the payload from the hook event and deliver it yourself to jenkins and see what happens, if it works then login to the administration SSH on GHE and try the request from there.

          My organisation is using GHE 2.8 with webhooks and it works great.

          Tim Jacomb added a comment - Try taking the payload from the hook event and deliver it yourself to jenkins and see what happens, if it works then login to the administration SSH on GHE and try the request from there. My organisation is using GHE 2.8 with webhooks and it works great.

          Eric Dalling added a comment -

          We recently updated our version of Jenkins to 2.46.1 and our GitHub Branch Source Plugin to 2.0.5 and now the webhooks from GHE are working for both Pipeline and Multibranch Pipeline jobs.

          Eric Dalling added a comment - We recently updated our version of Jenkins to 2.46.1 and our GitHub Branch Source Plugin to 2.0.5 and now the webhooks from GHE are working for both Pipeline and Multibranch Pipeline jobs.

          James Dumay added a comment - - edited

          stephenconnolly I remembered that you mention this on our call the other day - would happen after the reunification work?

          EDIT: english

          James Dumay added a comment - - edited stephenconnolly I remembered that you mention this on our call the other day - would happen after the reunification work? EDIT: english

          I am closing this as a duplicate of JENKINS-33228 as I believe if the GitHub plugin's server configuration is correctly configured and allowed to manage hooks then this issue is resolved, so as a result I claim the issue is the duplicate configuration.

          Stephen Connolly added a comment - I am closing this as a duplicate of JENKINS-33228 as I believe if the GitHub plugin's server configuration is correctly configured and allowed to manage hooks then this issue is resolved, so as a result I claim the issue is the duplicate configuration.

            Unassigned Unassigned
            eric_dalling Eric Dalling
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: