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

BitBucket fails to notify the branch source plugin

XMLWordPrintable

      I have the `Webhook to Jenkins for Bitbucket Server` plugin for Bitbucket Server. The plugin on push sends a notify request to Jenkins which is then supposed to go fetch the changes based on the notified changes json and run.

      What I'm seeing is that the webhook is firing the notify but Jenkins is not receiving the call, as far as I can tell based on the logs.

      See - https://mohamicorp.atlassian.net/servicedesk/customer/portal/2/MS-1395 for a ticket I have open with the Bitbucket plugin for this same issue, I'm attacking it from both ends.

       

      Below is the debug logs from Bitbucket showing the request go out.

      2018-10-03 08:57:58,406 DEBUG [JenkinsWebhook:thread-55]  c.n.s.w.n.BitbucketSourceNotifier Successfully triggered jenkins with url 'http://dev-scripts01:8088/bitbucket-scmsource-hook/notify':
      
      2018-10-03 08:57:58,407 DEBUG [JenkinsWebhook:thread-55]  c.n.s.w.n.BitbucketSourceNotifier Payload is : '{"repository":{"scmId":"git","project":{"key":"IN","name":"Investigations"},"slug":"investigations","links":{"self":[{"href":"http://sonofgojira.caseshare.com:7990/projects/IN/repos/investigations/browse"}]},"ownerName":"IN","public":false},"push":{"changes":[{"created":false,"closed":false,"new":{"type":"branch","name":"IN-56-research-implement-react-scripts-next","target":{"hash":"dbb9b4c7af6c7d8237a7fb15f052832d16e8574c","type":"commit"}},"old":{"type":"branch","name":"IN-56-research-implement-react-scripts-next","target":{"hash":"49a0037f05d2c7c70485863abac7e0e8d89bf92e","type":"commit"}}}]}}':

      However there are no logs in Jenkins that it ever received the notification. I've reviewed the `All Log` as well as created my own based on `com.cloudbees.jenkins.plugins.bitbucket` logger. The second log shows nothing and the all log has no details about it being notified.

       

      This was working as of 4 weeks ago or so and nothing has changed in the jobs, server configs, or hardware that would indicate this to be a configuration problem.

      If I scan the Organization Folder, Jenkins will reach out to Bitbucket and resolve the Jenkins files and see that there are changes to be ran. I can also trigger builds manually.

       

      Jenkins v2.131

      Bitbucket branch source plugin v2.2.12

            Unassigned Unassigned
            jbaumgardt Jeff Baumgardt
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: