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

Internal Server Error from Bitbucket when attempting to index branches

    Details

    • Similar Issues:

      Description

      After configuring a new multibranch pipeline job with a bitbucket branch source targeting bitbucket cloud, branch indexing returns this error:

      Started
      Connecting to https://bitbucket.org using jordan@rigup.com/******
      Looking up rigup/rigup-build for branches
      FATAL: Failed to recompute children of RigUp Main Build
      com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 500: INTERNAL SERVER ERROR.
      {"error": {"message": "Internal server error", "id": "66ccda07d9d24c928c6f554c39022eb8"}}
      	at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRequest(BitbucketCloudApiClient.java:432)
      	at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getBranches(BitbucketCloudApiClient.java:225)
      	at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource.retrieveBranches(BitbucketSCMSource.java:323)
      	at com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource.retrieve(BitbucketSCMSource.java:279)
      	at jenkins.scm.api.SCMSource.fetch(SCMSource.java:148)
      	at jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:294)
      	at com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:157)
      	at com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:122)
      	at hudson.model.ResourceController.execute(ResourceController.java:98)
      	at hudson.model.Executor.run(Executor.java:404)
      Finished: FAILURE
      

      The plugin is successfully authenticating with bitbucket, as the webhook is registered for the target repository.

        Attachments

          Issue Links

            Activity

            Hide
            mbertrand80 Marcus Bertrand added a comment -

            Hi all,

            I work on the Bitbucket Cloud dev team and am working a similar sounding case with our support team. Looking at the plugin, I can see that it is still using Bitbucket Cloud's very outdated, and deprecated, 1.0 API endpoint for listing branches. The 1.0 API tries to include a diff stat with every branch, causing repositories with a lot of branches & tags (yes, and tags) to hit Bitbucket Cloud's internal timeouts for API performance.

            To resolve this issue, the plugin should switch to using the more modern 2.0 API for gathering branch information. The endpoint for getting branch refs is

            https://api.bitbucket.org/2.0/repositories/{username}/{repo_slug}/refs/branches

            Cheers,
            Marcus Bertrand

            Show
            mbertrand80 Marcus Bertrand added a comment - Hi all, I work on the Bitbucket Cloud dev team and am working a similar sounding case with our support team. Looking at the plugin , I can see that it is still using Bitbucket Cloud's very outdated, and deprecated, 1.0 API endpoint for listing branches. The 1.0 API tries to include a diff stat with every branch, causing repositories with a lot of branches & tags (yes, and tags) to hit Bitbucket Cloud's internal timeouts for API performance. To resolve this issue, the plugin should switch to using the more modern 2.0 API for gathering branch information. The endpoint for getting branch refs is https: //api.bitbucket.org/2.0/repositories/{username}/{repo_slug}/refs/branches Cheers, Marcus Bertrand
            Hide
            jamesdumay James Dumay added a comment -

            Marcus Bertrand I am flagging this for a future technical debt sprint we are planning.

            Show
            jamesdumay James Dumay added a comment - Marcus Bertrand I am flagging this for a future technical debt sprint we are planning.
            Hide
            jamesdumay James Dumay added a comment -

            Opened JENKINS-45497 to track moving the API usage over to v2.

            Show
            jamesdumay James Dumay added a comment - Opened JENKINS-45497 to track moving the API usage over to v2.

              People

              • Assignee:
                amuniz Antonio Muñiz
                Reporter:
                mccoyjordan Jordan McCoy
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: