BitbucketCloudApiClient.executeMethod hangs the build

Your checklist for this issue

• Jenkins version

• Plugin version

• Bitbucket cloud

• Bitbucket server and version

Description

Jenkins: 2.217 Plugin: 2.6.0 Bitbucket: cloud

Since a couple of days ago almost all our builds hang before even printing anything.

The only thing I could find initially was when I cancel the hanged build it shows this message:

Branch event
java.lang.InterruptedException: sleep interrupted
	at java.lang.Thread.sleep(Native Method)
	at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.executeMethod(BitbucketCloudApiClient.java:858)
	at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRequestAsInputStream(BitbucketCloudApiClient.java:885)
	at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRequest(BitbucketCloudApiClient.java:909)
	at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getAllBranches(BitbucketCloudApiClient.java:1029)
	at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getBranchesByRef(BitbucketCloudApiClient.java:484)
	at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getBranches(BitbucketCloudApiClient.java:474)
	at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource.retrieve(BitbucketSCMSource.java:791)
	at jenkins.scm.api.SCMSource.fetch(SCMSource.java:582)
	at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:98)
	at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:299)
	at hudson.model.ResourceController.execute(ResourceController.java:97)
	at hudson.model.Executor.run(Executor.java:428)
Finished: FAILURE

Then I added a Logger for com.cloudbees.jenkins.plugins.bitbucket and it keeps printing this line over and over

Jan 27, 2020 11:10:42 PM FINE com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient
Bitbucket Cloud API rate limit reached, sleeping for 5 sec then retry...

To me, it seems like the build is hanging on trying to get the Jenkinsfile from bitbucket. Not sure why we suddenly reached the limit, because we are not building more PR than usual. Could Bitbucket now consider retry as a request toward the limit?

[jetersen]

I still think fix the PR #277 adds value even though they plan to roll it back 😆

[dblanchette]

I also have a support case open and got a reply:

We have recently made changes to our API rate limit for repository Refs, to be in line with our API limits are documented here: https://confluence.atlassian.com/bitbucket/rate-limits-668173227.html so all authenticated calls per user per hour to the repository endpoint are limited to 1k an hour. Our Dev team is working to revert those changes and increase the limit for branches endpoint calls. Once those changes are rolled out later today you shouldn’t be facing this again with Bitbucket, apologies for this inconvenience.