I am currently working on a Project. As part of that, we need to understand how many webhooks we can configure against each repo in a single project or single repo. As per the information from the Atlassian link, there is a limit of 50 webhooks against each repo. However, I have configured more than 60 webhooks in my repo but still, bitbucket has allowed creating the same, and requests were triggered. Please can you help me understand in which scenarios the limit is imposed by BitBucket?
Hi @Kishore V and welcome to the community.
The documentation you linked is for Bitbucket Cloud and it applies to Bitbucket Cloud repos (repos hosted in https://bitbucket.org/). It is not applicable for repos in Bitbucket Server (self-hosted instance).
While viewing the documentation, you can see that the option Cloud in the top right corner is selected, you can switch to Server documentation by selecting the option Data center and Server next to it.
Are you using Bitbucket Cloud (https://bitbucket.org/) or Bitbucket Server?
For Bitbucket Cloud, the support team can also override this limit for a certain workspace if an admin reaches out to us and they need to use more webhooks. So, if you're using a Bitbucket Cloud repo, one of the admins may have reached out to use to override this limit.
There is no such limit for Bitbucket Server.
Please take note though of the section titled Circuit breaking in the following documentation about Bitbucket Server webhooks:
A webhook may also be skipped if there are too many webhooks in flight. If there are 250 webhooks being invoked, further requests will be skipped until the number in flight drops below 250.
These limits are entirely configurable if your instance has different requirements. For more information, see Configuration properties.
Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...