-
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