djr2 added a comment - 08/Sep/2019 11:38 PM Attachment 674685869-Screen%20Shot%202018-07-18%20at%203.42.36%20PM.png has been added with description: Originally embedded in Bitbucket issue #16710 in site/master

djr2 added a comment - 08/Sep/2019 11:38 PM Attachment 52593289-Screen%20Shot%202018-07-18%20at%203.42.18%20PM.png has been added with description: Originally embedded in Bitbucket issue #16710 in site/master

djr2 added a comment - 08/Sep/2019 11:38 PM Attachment 2470682953-Screen%20Shot%202018-07-18%20at%208.36.56%20PM%20copy.png has been added with description: Originally embedded in Bitbucket issue #16710 in site/master

djr2 added a comment - 25/Jul/2018 1:48 PM Atlassian fixed the issue

Michael Bom added a comment - 20/Jul/2018 6:04 AM @djr2 Good luck

djr2 added a comment - 19/Jul/2018 5:06 PM @mbom its working! They just emailed me a bit ago and I just had time run a test just now. Guess I can go through all the jenkins projects and turn off auto polling now. ugh

Michael Bom added a comment - 19/Jul/2018 3:34 PM @djr2 Looks like it is working again, can you confirm it is working for you?

Michael Bom added a comment - 19/Jul/2018 12:03 PM @djr2 Ok, thank you!

djr2 added a comment - 19/Jul/2018 12:00 PM @mbom I opened a support ticket and had it escalated last night. I'm going to refer them to you so they can also test against your domain/hook.

Michael Bom added a comment - 19/Jul/2018 11:54 AM We have the same issue, also no changes in DNS. Seems like a problem on Atlassian side. Please let us know when this issue is resolved, since this is really interrupting our development. We now need to manually trigger builds!

djr2 added a comment - 19/Jul/2018 12:54 AM I was able to manually post using a Bitbucket API payload from a previous successful hook just fine using Paw This is definitely an issue with Bitbucket

djr2 added a comment - 18/Jul/2018 8:45 PM We are being denied access to the API. The same user that receives the hook can push/pull just fine Jul 18, 2018 8:28:40 PM WARNING com.cloudbees.jenkins.plugins.bitbucket.hooks.WebhookAutoRegisterListener$1 doRun Could not register hooks for ***** com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 403: Forbidden. Forbidden at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRequestAsInputStream(BitbucketCloudApiClient.java:744) at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRequest(BitbucketCloudApiClient.java:756) at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getWebHooks(BitbucketCloudApiClient.java:530) Caused: java.io.IOException: I/O error when parsing response from URL: https: //api.bitbucket.org/2.0/repositories /****/ ****/hooks?page=1&pagelen=50 at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getWebHooks(BitbucketCloudApiClient.java:544) at com.cloudbees.jenkins.plugins.bitbucket.hooks.WebhookAutoRegisterListener.registerHooks(WebhookAutoRegisterListener.java:143) at com.cloudbees.jenkins.plugins.bitbucket.hooks.WebhookAutoRegisterListener.access$000(WebhookAutoRegisterListener.java:64) at com.cloudbees.jenkins.plugins.bitbucket.hooks.WebhookAutoRegisterListener$1.doRun(WebhookAutoRegisterListener.java:110) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:72) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang. Thread .run( Thread .java:748)