[JIRA] (JENKINS-55649) X-Bitbucket-Type header / server_url request parameter not found

5 views
Skip to first unread message

christoph.forster@swarovski.com (JIRA)

unread,
Jan 17, 2019, 7:12:02 AM1/17/19
to jenkinsc...@googlegroups.com
Christoph Forster created an issue
 
Jenkins / Bug JENKINS-55649
X-Bitbucket-Type header / server_url request parameter not found
Issue Type: Bug Bug
Assignee: Unassigned
Components: bitbucket-branch-source-plugin
Created: 2019-01-17 12:10
Priority: Major Major
Reporter: Christoph Forster

We're using Bitbucket Server 5.9.1, Jenkins 2.159 and bitbucket-branch-source-plugin 2.4.0.

The automatic creation of the Webhook within Bitbucket works without any problems but when the repository changes (e.g. because of a push) we receive the following Error in Jenkins:

X-Bitbucket-Type header / server_url request parameter not found. Bitbucket Cloud webhook incoming.
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

christoph.forster@swarovski.com (JIRA)

unread,
Jan 17, 2019, 10:09:01 AM1/17/19
to jenkinsc...@googlegroups.com
Christoph Forster updated an issue
Change By: Christoph Forster
We're using Bitbucket Server 5.9.1, Jenkins 2.159 and bitbucket-branch-source-plugin 2.4.0.

The automatic creation of the Webhook within Bitbucket works without any problems but when the repository changes (e.g. because of a push) we receive the following Error in Jenkins:

{code}

X-Bitbucket-Type header / server_url request parameter not found. Bitbucket Cloud webhook incoming.
{code}

And the underlying Multibranch Pipelines are not triggered

christoph.forster@swarovski.com (JIRA)

unread,
Jan 17, 2019, 10:11:04 AM1/17/19
to jenkinsc...@googlegroups.com
Christoph Forster updated an issue
We're using Bitbucket Server 5.9.1, Jenkins 2.159 and bitbucket-branch-source-plugin 2.4.0.

The automatic creation of the Webhook within Bitbucket works without any problems but when the repository changes (e.g. because of a push) we receive the following Error in Jenkins:

{code}
X-Bitbucket-Type header / server_url request parameter not found. Bitbucket Cloud webhook incoming.
{code}

And the underlying Multibranch Pipelines are not triggered .

I also checked: The Server URL is configured within Bitbucket

gpxricky@gmx.de (JIRA)

unread,
Feb 6, 2019, 9:58:02 AM2/6/19
to jenkinsc...@googlegroups.com
GPX Ricky commented on Bug JENKINS-55649
 
Re: X-Bitbucket-Type header / server_url request parameter not found

I have the same issue. We are using bitbucket-branch-source-plugin 2.4.0 and Bitbucket Server 5.9.0.

kobus.jacek@gmail.com (JIRA)

unread,
Feb 13, 2019, 6:26:02 AM2/13/19
to jenkinsc...@googlegroups.com

Im using multibranch setup and since this morning no new builds are triggered. I only see this message in logs.

It started happening with version 2.3 of this plugin, so I've updated all plugins, now the same thing happens with 2.4.1.

Jenkins 2.150.2, Bitbucket cloud.

kobus.jacek@gmail.com (JIRA)

unread,
Feb 13, 2019, 6:46:02 AM2/13/19
to jenkinsc...@googlegroups.com
Jacek edited a comment on Bug JENKINS-55649
Im using multibranch setup and since this morning no new builds are triggered. I only see this message in logs.

It started happening with version 2.3 of this plugin, so I've updated all plugins, now the same thing happens with 2.4.1.

Jenkins 2.150.2, Bitbucket cloud.


 
Update: 

In my case it was:

{noformat}
com.cloudbees.jenkins.plugins.bitbucket.api.BitbucketRequestException: HTTP request error. Status: 403: Forbidden.
Too many invalid password attempts. Log in at https://id.atlassian.com/ to restore access.
{noformat}

It was not related to the log message in this task.

darin_patrick@csx.com (JIRA)

unread,
Feb 19, 2019, 5:23:02 PM2/19/19
to jenkinsc...@googlegroups.com

I am also experiencing the same issue. 

However I was able to work around the issue by adding the server_url parameter to the webhook URL.

https://<JENKINS_URL>/bitbucket-scmsource-hook/notify?server_url=<BITBUCKET_SERVER_URL>

benjamin.brummer@pinteam.eu (JIRA)

unread,
Feb 22, 2019, 4:47:03 AM2/22/19
to jenkinsc...@googlegroups.com

When i let the plugin manage the hooks it configures the webhook on Bitbucket to be https://jenkins.company.com/bitbucket-scmsource-hook/notify?server_url=https%3A%2F%2Fbitbucket.company.com. Similar to Darin Patrick's comment. It works without any problem. Maybe this simply needs to be updated in the plugin wiki?

benjamin.brummer@pinteam.eu (JIRA)

unread,
Feb 22, 2019, 4:48:02 AM2/22/19
to jenkinsc...@googlegroups.com
Benjamin Brummer edited a comment on Bug JENKINS-55649
When i let the plugin manage the hooks it configures the webhook on Bitbucket to be [
{code:java}
 https://jenkins.company.com/bitbucket-scmsource-hook/notify?server_url=https%3A%2F%2Fbitbucket.company.com .]
{code}
 Similar to [~dpat65]'s comment. It works without any problem. Maybe this simply needs to be updated in the plugin wiki?

rhierlmeier@gmail.com (JIRA)

unread,
Jul 1, 2019, 2:58:02 AM7/1/19
to jenkinsc...@googlegroups.com

The workaround is not working for me. We are using Jenkins 2.164.3, bitbucket-branch-source-plugin 2.4.4 and Bitbucket server 5.6.1.
I enabled the system logs for the logger com.cloudbees.jenkins.plugins.bitbucket.
It prints the following logs when a change to a PR was pushed:

Jul 01, 2019 8:48:13 AM FINE com.cloudbees.jenkins.plugins.bitbucket.hooks.BitbucketSCMSourcePushHookReceiver
X-Bitbucket-Type header / server_url request parameter not found. Bitbucket Cloud webhook incoming.
Jul 01, 2019 8:48:13 AM FINE com.cloudbees.jenkins.plugins.bitbucket.hooks.BitbucketSCMSourcePushHookReceiver
server_url request parameter found. Bitbucket Native Server webhook incoming.

christoph.forster@swarovski.com (JIRA)

unread,
Dec 4, 2019, 2:24:04 AM12/4/19
to jenkinsc...@googlegroups.com

For me the Workaround also works.
rhierlmeier: The log shows that the server_url Parameter is found and is working as expected so your problem must be within the job configuration
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

christoph.forster@swarovski.com (JIRA)

unread,
Dec 4, 2019, 2:25:06 AM12/4/19
to jenkinsc...@googlegroups.com
Christoph Forster closed an issue as Won't Fix
 
Change By: Christoph Forster
Status: Open Closed
Resolution: Won't Fix

christoph.forster@swarovski.com (JIRA)

unread,
Dec 4, 2019, 2:26:04 AM12/4/19
to jenkinsc...@googlegroups.com
Christoph Forster edited a comment on Bug JENKINS-55649
For me the " Workaround " also works.
[~rhierlmeier]: The log shows that the server_url Parameter is found and is working as expected so your problem must be within the job configuration
Reply all
Reply to author
Forward
0 new messages