Hello, I am facing a problem and I wouldn’t know if it’s a rate limit issue or a Jenkins issue:
I have many pipelines configured with Organization Folders, each containing many repositories. For each of them, we use the Bitbucket Branch Source Plugin to automatically create multi-branch jobs and manage webhooks with Bitbucket, and we believe that because of this, we are hitting Bitbucket’s API request limits.
In conversation with the Atlassian team, they advised us to use Access Tokens to distribute the load among the pipelines. However, the version 2.456 of Jenkins we use is not compatible with Access Tokens, so we resorted to using multiple service accounts and distributed them across our pipelines, connecting each of them to Jenkins using App Password.
With the mentioned solution, I mitigated the problem, but even so, every day I am facing many communication delays between Bitbucket Cloud and my Jenkins. The jobs take a long time to be triggered via webhook, and I continue to receive rate limit issues
→
Jenkins setup:
Jenkins 2.456
Bitbucket PluginVersão254.v9d8ec33a_7a_42