• Type: Bug
• Resolution: Unresolved
• Priority: Minor
• Component/s: atlassian-bitbucket-server-integration-plugin
• Labels:

  • pull-request
  • triaged
  • webhook

1. 

   jenkins.PNG

   16 kB

   2022-05-20 09:39

[JENKINS-68589] Provide sysprop option to disregard HTTP/HTTPS protocol when accepting webhooks

Farshid Abdollahi created issue - 2022-05-20 09:40

Martin Henschke made changes - 2022-05-26 01:32

Description	Original: I've configured plugin and pipeline as described in tutorial all test connections from Jenkins side and Bitbucket side works well. I built pipeline successfully and status updated on Bitbucket server. When Bitbucket is sending request with webhook, it doesn't trigger my pipeline and I'm receiving a base URL not match info inside Jenkins logs. Jenkins has access through http to Bitbucket and Bitbucket base URL is https. Is it important?	New: In cases where Bitbucket is servicing requests behind a firewall, it may be identified by both a HTTP and HTTPS url. This bug requires creating the option to ignore the protocol when accepting webhooks so that webhooks served from a HTTPS Bitbucket are not treated by Jenkins as coming from a separate host. Original ticket: I've configured plugin and pipeline as described in tutorial all test connections from Jenkins side and Bitbucket side works well. I built pipeline successfully and status updated on Bitbucket server. When Bitbucket is sending request with webhook, it doesn't trigger my pipeline and I'm receiving a base URL not match info inside Jenkins logs. Jenkins has access through http to Bitbucket and Bitbucket base URL is https. Is it important?
Summary	Original: Webhook can't trigger pipeline	New: Provide sysprop option to disregard HTTP/HTTPS protocol when accepting webhooks

Martin Henschke made changes - 2022-05-26 01:33

Labels

Original: pull-request webhook

New: pull-request triaged webhook

Martin Henschke made changes - 2022-06-08 23:21

Link

New: This issue is duplicated by JENKINS-68496 [ JENKINS-68496 ]