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

WEBhook return error 400 when trigered from push

XMLWordPrintable

    • 2.1.3

      Hi

      I try to integrate Jennkins and Bitbucket server with "Bitbucket Server Integration" plugin. I configure personal access token and after pipeline job creation webhook is created in Bitbucket server. Git access is working and status from Jenkins job is presented in Bitbucket server.

      The problem that I have is with triggering Jenkins job on git push. I receive this error in Bitbucket WEBhook:

       

       

      Date: Wed, 24 Jun 2020 07:40:05 GMT
      Server: Jetty(9.4.27.v20200227)
      X-Content-Type-Options: nosniff
      Cache-Control: must-revalidate,no-cache,no-store
      Content-Type: text/html; charset=ISO-8859-1
      Via: 1.1 localhost (Apache-HttpClient/4.5.5 (cache))
      Content-Length: 1468
      Body
      <html>
      <head>
      <meta http-equiv="Content-Type" content="text/html;charset=utf-8"/>
      <title>Error 400 Failed to parse the body: Cannot construct instance of `com.atlassian.bitbucket.jenkins.internal.model.BitbucketUser`, problem: emailAddress
       at [Source: (org.eclipse.jetty.server.HttpInputOverHTTP); line: 1, column: 311] (through reference chain: com.atlassian.bitbucket.jenkins.internal.trigger.RefsChangedWebhookEvent[&quot;actor&quot;])</title>
      </head>
      

       

      and this error in Jenkins log:

      PM SCHWERWIEGEND com.atlassian.bitbucket.jenkins.internal.trigger.BitbucketWebhookEndpoint parseFailed to parse the body: Cannot construct instance of `com.atlassian.bitbucket.jenkins.internal.model.BitbucketUser`, problem: emailAddress
       at [Source: (org.eclipse.jetty.server.HttpInputOverHTTP); line: 1, column: 311] (through reference chain: com.atlassian.bitbucket.jenkins.internal.trigger.RefsChangedWebhookEvent["actor"])
      

       

            mhenschke_atlassian Martin Henschke
            niki_kan Nikolay Kanchev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: