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">"key"</span>: [<span class="code-quote" style="color: #009100">"Ensure <span class="code-keyword" style="color: #000091; color: #009100">this</span> value has at most 40 characters (it has 54)."</span>]}, <span class="code-quote" style="color: #009100">"message"</span>: <span class="code-quote" style="color: #009100">"Bad request"</span>}}

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web16

  • via Google Groups by pavly...@yandex.by (JIRA), 11 months ago
    class="code-quote" style="color: #009100">"Ensure <span class="code-keyword" style="color: #000091; color: #009100">this</span> value has at most 40 characters (it has 54)."</span>]}, <span class="code-quote" style="color: #009100">"message"</span>: <span class="code-quote" style="color: #009100">"Bad request"</span>}}
  • via Google Groups by james....@gmail.com (JIRA), 9 months ago
    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
  • via Jenkins JIRA by Mikhail Paulyshka, 9 months ago
    HTTP request error. Status: 400: BAD REQUEST. {"error": {"fields": {"key": ["Ensure this value has at most 40 characters (it has 54)."]}, "message": "Bad request"}}
  • Stack trace

    • 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">"key"</span>: [<span class="code-quote" style="color: #009100">"Ensure <span class="code-keyword" style="color: #000091; color: #009100">this</span> value has at most 40 characters (it has 54)."</span>]}, <span class="code-quote" style="color: #009100">"message"</span>: <span class="code-quote" style="color: #009100">"Bad request"</span>}} 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:206) at hudson.model.ResourceController.execute(ResourceController.java:98) at hudson.model.Executor.run(Executor.java:404)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.