Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Bitbucket Rate Limit during clone, fetch


We are currently facing a build fail by Jenkins when it attempts to fetch the repositories. For a few projects that has data size less than 2Mb, the operations went well. When Jenkins attempt to fetch projects that has data size of 100Mb or less, the operation fails.

Is there a rate limit for project with large data size ?




1 answer

0 votes
Patrik S Atlassian Team Jul 05, 2022

Hello @Andrew Liew ,

Thank you for reaching out to Atlassian Community.

We do have some API rate limits implemented to grant stability across our platform, but those limits are based on the number of requests, and not on the size of the repository. The number of API calls is measured as follows: 

  • Unauthenticated calls: measured against a specific IP address.

  • Authenticated calls: measured against the user ID.

The limits of each kind of request are outlined in the following documentation : 

Having said that, if your Jenkins instance is using the pooling method to check for changes in the repo, meaning that it will be frequently calling the bitbucket API to check if a new build should be triggered, the user used by Jenkins to authenticate might be affected by the API rate limiting, depending on the number of calls per rolling hour. When a user is affected by rate limiting, we return a 429 HTTP status code to the request.

If that is the case, to avoid this limitation you can either reduce the pooling rate of your Jenkins instance, so it calls bitbucket API less frequently, or implement the usage of Bitbucket Webhooks, so bitbucket itself will send a request to your Jenkins instance when a given event happened to the repository (for example a new push)

Checking our internal tools I've noticed you have access to a workspace in a Premium subscription, so in case you want us to check our internal logs to confirm if your Jenkins requests are being rate limited, you can raise a support ticket with us in the following link : 

Thank you, @Andrew Liew !

Kind regards,

Patrik S

Suggest an answer

Log in or Sign up to answer
Site Admin

Atlassian Community Events