We have a team repository with about 300 repositories which is scanned for jenkins files.
We updated Bitbucket-branch-source-plugin to 2.1.0 (working version 1.9) yesterday and now we hit the rate limit every time.
This means that repositories that are last in the arbitrarily sorted list is never added. We think that this plugin should know about the rate limit and throttle it self. It should always handle newly updated repositories first.
The best solution would be if Atlasian created a webhook in the team resource for repository creation. But we need a workaround in the mean time.