-
Bug
-
Resolution: Unresolved
-
Minor
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?
- is duplicated by
-
JENKINS-68496 Build trigger using Bitbucket webhook not working
-
- Closed
-
Hi Farshid, thanks for raising this ticket.
Based on the information you've provided I suspect this is a configuration issue, but I need to know a bit more about your setup first. When you say Jenkins is using a HTTP url but your Bitbucket base URL is HTTPS, are you operating Bitbucket behind a load balancer, but using one of the HTTP nodes as your jenkins configured base URL?
The fact that the protocols is different is probably less significant than that the URLs themselves are different. Our plugin accepts a webhook from an instance expecting the URL from which the request originates, and we use that to identify which server instances are applicable for a given job. If the URLs don't match, we assume different hosts and do not build.
If it is possible to use the HTTPS url the webhook is originating from rather than the HTTP url, I expect this problem will be resolved unless there's a reason we can't use that URL- in which case could you let me know, and we can potentially open a feature request given your use case.
Thanks,
Martin