Does status/build throttle with 404s?


#1

The jenkins bitbucket-pullrequest-builder plugin is using this api call:

https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/{username}/{repo_slug}/commit/{node}/statuses/build/{key}

I am receiving errors like this from the endpoint, and I know that the build and commit both exist, and can be seen in the activity log from bitbucket:

Jan 29, 2019 6:49:01 PM bitbucketpullrequestbuilder.bitbucketpullrequestbuilder.bitbucket.ApiClient send WARNING: Response status: HTTP/1.1 404 Not Found URI: https://bitbucket.org/api/2.0/repositories/ACCT/REPO/commit/SH_HASH/statuses/build/jenkins-HASH
Jan 29, 2019 6:49:01 PM bitbucketpullrequestbuilder.bitbucketpullrequestbuilder.bitbucket.ApiClient send WARNING: {"type": "error", "error": {"message": "Build status with key 'jenkins-HASH' for node HASH repository REPO not found"}}

The behavior is sporadic - I see it from several different repos in our jenkins log file. The repos and hashes absolutely exist, so, I’m wondering if maybe I’m hitting throttling or something.


#2

Hello,
None of the Bitbucket Cloud API endpoints return 404 for rate limiting. This is probably best to move to a support ticket so we can track down the problem for you.

https://getsupport.atlassian.com/servicedesk/customer/portal/11