com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 500: INTERNAL SERVER ERROR. {"error": {"message": "Internal server error", "id": "66ccda07d9d24c928c6f554c39022eb8"}}

Google Groups | mccoy....@gmail.com (JIRA) | 2 months ago
  1. 0

    [JIRA] (JENKINS-38820) Internal Server Error from BitBucket when attempting to index branches

    Google Groups | 2 months ago | mccoy....@gmail.com (JIRA)
    com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 500: INTERNAL SERVER ERROR. {"error": {"message": "Internal server error", "id": "66ccda07d9d24c928c6f554c39022eb8"}}
  2. 0

    [JIRA] (JENKINS-36029) multibranch-job deleted when bitbucket communication fails

    Google Groups | 6 months ago | asg...@gmail.com (JIRA)
    com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 401: No Autorizado.<br> {"errors":[</p> {"context":null,"message":"Authentication failed. Please check your credentials and try again.","exceptionName":"com.atlassian.bitbucket.auth.AuthenticationSystemException"} <p style="margin: 10px 0 0 0">]}<br>
  3. 0

    This is essentially the same issue as JENKINS-32781, occurs when using the latest version of the plugin built off master (testing out new build status notifications). Bitbucket requires the key to be <= 40 characters but it looks like right now the job name is being used which for my case with pipelines would be the branch name which is typically fairly long because we're using auto generated branch names from Jira (uses jira number + title). Also, I'm not sure what the desired uniqueness is here but in JENKINS-32781 the key is the project name + build number so each build can have a unique status e.g. built once and tests were flakey and it failed but then built again and it passed - depends if you want the build status to record both runs or just the latest one. The diff from JENKINS-32781 for reference - https://github.com/jenkinsci/bitbucket-build-status-notifier-plugin/commit/d73ec91ad424e4f885a7961579a55ccf1299d5e2 Callstack for reference on failed builds (created a long branch name to test this): {code} [Bitbucket] Notifying commit build result com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 400: BAD REQUEST. {"error": {"fields": {"key": ["Ensure this value has at most 40 characters (it has 119)."]}, "message": "Bad request"}} at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.postRequest(BitbucketCloudApiClient.java:486) at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.postRequest(BitbucketCloudApiClient.java:513) at com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.postBuildStatus(BitbucketCloudApiClient.java:303) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketChangesetCommentNotifier.buildStatus(BitbucketChangesetCommentNotifier.java:49) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketBuildStatusNotifications.createBuildCommitStatus(BitbucketBuildStatusNotifications.java:85) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketBuildStatusNotifications.sendNotifications(BitbucketBuildStatusNotifications.java:171) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketBuildStatusNotifications.access$000(BitbucketBuildStatusNotifications.java:60) at com.cloudbees.jenkins.plugins.bitbucket.BitbucketBuildStatusNotifications$JobCheckOutListener.onCheckout(BitbucketBuildStatusNotifications.java:190) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:123) at org.jenkinsci.plugins.workflow.cps.CpsScmFlowDefinition.create(CpsScmFlowDefinition.java:108) at org.jenkinsci.plugins.workflow.multibranch.SCMBinder.create(SCMBinder.java:85) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:207) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:410) Finished: FAILURE {code}

    Jenkins JIRA | 3 months ago | Ryan Rupp
    com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 400: BAD REQUEST. {"error": {"fields": {"key": ["Ensure this value has at most 40 characters (it has 119)."]}, "message": "Bad request"}}
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    [JIRA] (JENKINS-38664) bitbucket source plugin fails with bad URL

    Google Groups | 2 months ago | james....@gmail.com (JIRA)
    com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 400: BAD REQUEST. {<span class="code-quote" style="color: #009100">"error"</span>: {<span class="code-quote" style="color: #009100">"fields"</span>: {<span class="code-quote" style="color: #009100">"url"</span>: [<span class="code-quote" style="color: #009100">"Enter a valid URL."</span>]}, <span class="code-quote" style="color: #009100">"message"</span>: <span class="code-quote" style="color: #009100">"Bad request"</span>}}
  6. 0

    [JIRA] [bitbucket-branch-source-plugin] (JENKINS-34262) Support for OAuth credentials

    Google Groups | 8 months ago | maxim....@gmail.com (JIRA)
    com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 401: UNAUTHORIZED.

    1 unregistered visitors
    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. 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()
    2. com.cloudbees.jenkins
      BitbucketSCMSource.retrieve
      1. com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getRequest(BitbucketCloudApiClient.java:432)
      2. com.cloudbees.jenkins.plugins.bitbucket.client.BitbucketCloudApiClient.getBranches(BitbucketCloudApiClient.java:225)
      3. com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource.retrieveBranches(BitbucketSCMSource.java:323)
      4. com.cloudbees.jenkins.plugins.bitbucket.BitbucketSCMSource.retrieve(BitbucketSCMSource.java:279)
      4 frames
    3. jenkins.scm.api
      SCMSource.fetch
      1. jenkins.scm.api.SCMSource.fetch(SCMSource.java:148)
      1 frame
    4. jenkins.branch
      MultiBranchProject.computeChildren
      1. jenkins.branch.MultiBranchProject.computeChildren(MultiBranchProject.java:294)
      1 frame
    5. com.cloudbees.hudson
      FolderComputation.run
      1. com.cloudbees.hudson.plugins.folder.computed.ComputedFolder.updateChildren(ComputedFolder.java:157)
      2. com.cloudbees.hudson.plugins.folder.computed.FolderComputation.run(FolderComputation.java:122)
      2 frames
    6. Hudson
      Executor.run
      1. hudson.model.ResourceController.execute(ResourceController.java:98)
      2. hudson.model.Executor.run(Executor.java:404)
      2 frames