Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-45497

Move BitbucketCloudApiClient to Bitbucket v2

    XMLWordPrintable

Details

    • Blue Ocean 1.3, Blue Ocean 1.4 - beta 1, Blue Ocean 1.4 - beta 2

    Description

      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.

      Attachments

        Issue Links

          Activity

            jamesdumay James Dumay created issue -
            jamesdumay James Dumay made changes -
            Field Original Value New Value
            Labels cloudbees-internal-pipeline cloudbees-internal-pipeline technical-debt
            jamesdumay James Dumay made changes -
            Link This issue is duplicated by JENKINS-38820 [ JENKINS-38820 ]
            jamesdumay James Dumay made changes -
            Assignee Antonio Muñiz [ amuniz ]
            dshmelev Dmitry Shmelev made changes -
            Priority Minor [ 4 ] Critical [ 2 ]

            Hi All!

            I can't init multibranch pipeline with bitbucket source plugin.

            Started
            [Wed Aug 02 13:27:17 UTC 2017] Starting branch indexing...
            Connecting to https://bitbucket.org using RepoOwner/****** (onetwotrip_bitbucket_app)
            Repository type: Git
            Looking up RepoOwner/repo for branches
            ERROR: [Wed Aug 02 13:28:18 UTC 2017] Could not fetch branches from source 61ea5900-2bb7-4889-b635-6ccbe5028f16
            java.net.SocketTimeoutException: Read timed out
            

            Me have many branches in repo, and this problem reproduced locally using curl and APIv1

            https://bitbucket.org/api/1.0/repositories/RepoOwner/repo/branches

            Atlassian support team reports

            Our development team has looked into the issue and the call is failing for this specific repository because there is a very large number of open branches. Version 1 of our API does not support pagination (as opposed to version 2) and this can cause issues when the responses are very large.
            

             

            dshmelev Dmitry Shmelev added a comment - Hi All! I can't init multibranch pipeline with bitbucket source plugin. Started [Wed Aug 02 13:27:17 UTC 2017] Starting branch indexing... Connecting to https: //bitbucket.org using RepoOwner/****** (onetwotrip_bitbucket_app) Repository type: Git Looking up RepoOwner/repo for branches ERROR: [Wed Aug 02 13:28:18 UTC 2017] Could not fetch branches from source 61ea5900-2bb7-4889-b635-6ccbe5028f16 java.net.SocketTimeoutException: Read timed out Me have many branches in repo, and this problem reproduced locally using curl and APIv1 https://bitbucket.org/api/1.0/repositories/RepoOwner/repo/branches Atlassian support team reports Our development team has looked into the issue and the call is failing for this specific repository because there is a very large number of open branches. Version 1 of our API does not support pagination (as opposed to version 2) and this can cause issues when the responses are very large.  
            jamesdumay James Dumay made changes -
            Assignee Vivek Pandey [ vivek ]
            jamesdumay James Dumay made changes -
            Epic Link JENKINS-35759 [ 171771 ]
            jamesdumay James Dumay added a comment -

            vivek would you mind taking care of this one at some point?

            jamesdumay James Dumay added a comment - vivek would you mind taking care of this one at some point?
            jamesdumay James Dumay made changes -
            Component/s blueocean-plugin [ 21481 ]
            Sprint Blue Ocean 1.3 - beta 1 [ 386 ]
            jamesdumay James Dumay made changes -
            Description 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.
            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.
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Priority Critical [ 2 ] Major [ 3 ]
            jamesdumay James Dumay made changes -
            Sprint Blue Ocean 1.3 [ 386 ] Blue Ocean 1.3, Blue Ocean 1.4 - beta 1 [ 386, 401 ]
            jamesdumay James Dumay made changes -
            Sprint Blue Ocean 1.3, Blue Ocean 1.4 - beta 1 [ 386, 401 ] Blue Ocean 1.3, Blue Ocean 1.4 - beta 1, Blue Ocean 1.4 - beta 2 [ 386, 401, 426 ]
            vivek Vivek Pandey made changes -
            Status Open [ 1 ] In Progress [ 3 ]
            vivek Vivek Pandey made changes -
            Status In Progress [ 3 ] In Review [ 10005 ]
            vivek Vivek Pandey added a comment - Fixed in PR https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/73 .
            vivek Vivek Pandey made changes -
            Resolution Fixed [ 1 ]
            Status In Review [ 10005 ] Resolved [ 5 ]
            stephenconnolly Stephen Connolly made changes -
            Remote Link This issue links to "Page (Jenkins Wiki)" [ 17974 ]
            kshultz Karl Shultz made changes -
            Labels cloudbees-internal-pipeline technical-debt cloudbees-internal-pipeline technical-debt testing-notes-not-applicable
            bitwiseman Liam Newman made changes -
            Status Resolved [ 5 ] Closed [ 6 ]

            People

              vivek Vivek Pandey
              jamesdumay James Dumay
              Votes:
              1 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: