-
Bug
-
Resolution: Unresolved
-
Critical
-
None
I am getting rate limit issues due to this. Looking into Multibranch Pipeline Events - I can see every time Jenkins gets a payload, it does a scan on all the refs instead of the one it gets in the payload i.e.
"type": "branch", "name": "name-of-branch",
The number of requests Jenkins makes to Bitbucket Server grows exponentially with a number of branches and pushes to them.
- causes
-
JENKINS-67502 cloudbees-bitbucket-branch-source latest version marks master branch as deleted
- Resolved
-
JENKINS-67538 Branches with newly pushed commits get disabled
- Resolved
- is related to
-
JENKINS-55071 Slow branch scan when using Bitbucket source
- Open
-
JENKINS-54983 Hitting Bitbucket API Rate limit quite easily
- Open
- links to