-
Improvement
-
Resolution: Fixed
-
Major
-
-
Blue Ocean 1.3, Blue Ocean 1.4 - beta 1, Blue Ocean 1.4 - beta 2
According to Atlassian's Bitbucket team we are using some inefficient API methods that cause undue load on their API endpoints.
BitbucketCloudApiClient uses a mixture of v1 and v2 APIs. We should switch solely over to Bitbucket v2 API to avoid load issues for Bitbucket and prevent a nasty surprise when they finally deprecate v1.
We need to ensure that pagination is also handled.
- is duplicated by
-
JENKINS-38820 Internal Server Error from Bitbucket when attempting to index branches
-
- Resolved
-
- mentioned in
-
Page Failed to load
[JENKINS-45497] Move BitbucketCloudApiClient to Bitbucket v2
Labels | Original: cloudbees-internal-pipeline | New: cloudbees-internal-pipeline technical-debt |
Link |
New:
This issue is duplicated by |
Assignee | Original: Antonio Muñiz [ amuniz ] |
Priority | Original: Minor [ 4 ] | New: Critical [ 2 ] |
Assignee | New: Vivek Pandey [ vivek ] |
Epic Link | New: JENKINS-35759 [ 171771 ] |
Component/s | New: blueocean-plugin [ 21481 ] | |
Sprint | New: Blue Ocean 1.3 - beta 1 [ 386 ] |
Description |
Original:
According to Atlassian's Bitbucket team we are using some inefficient API methods that cause undue load on their API endpoints. {{BitbucketCloudApiClient}} uses a mixture of v1 and v2 APIs. We should switch solely over to Bitbucket v2 API to avoid load issues for Bitbucket and prevent a nasty surprise when they finally deprecate v1. |
New:
According to Atlassian's Bitbucket team we are using some inefficient API methods that cause undue load on their API endpoints. {{BitbucketCloudApiClient}} uses a mixture of v1 and v2 APIs. We should switch solely over to Bitbucket v2 API to avoid load issues for Bitbucket and prevent a nasty surprise when they finally deprecate v1. We need to ensure that pagination is also handled. |
Rank | New: Ranked higher |
Rank | New: Ranked higher |