[JIRA] (JENKINS-47891) Bitbucket branch source plugin does not understand the new Bitbucket Server webhooks

[jimkli...@gmail.com (JIRA)]

Title: Message Title

Jim Klimov commented on JENKINS-47891   Re: Bitbucket branch source plugin does not understand the new Bitbucket Server webhooks The PR has now been completed, merged and made its way into the new release of the plugin. This worked nicely for our Multi-Branch Pipelines generated via Bitbucket team folder "jobs" that are the one item we configure "manually" to get our repos and branches discovered to spawn the pipeline jobs. A rescan of the organization "job" in Jenkins (after setting the global config to use the "Native" webhook implementation in the connector for our BB server) made configurations in all repos that had a Jenkinsfile in at least one branch, but no configurations in repos that had no such branches (corollary: to initially introduce pipeline support in codebase of a component, one has to rescan that organization or MBP job). One caveat I hit in our local setup (constrained by a web of corporate IT policies) was that our lab's Jenkins server uses a self-signed certificate which the centrally managed corporate Bitbucket Server instance reasonably does not trust, so it can not HTTP POST to. Our other consumers (developers' browsers and internal build farm) have no issues with trusting this certificate. I had to change the (apache httpd) reverse proxy handling to let it through as plaintext: RedirectMatch 302 ^(/(?!neo.*$|bitbucket-scmsource-hook$|bitbucket-scmsource-hook/.*$).*$) https://jenkins.domain.com/$1 ProxyPass /bitbucket-scmsource-hook http://jenkins.domain.com:8080/bitbucket-scmsource-hook/ nocanon connectiontimeout=3600 timeout=3600 retry=0 ...and had to change the Jenkins global config to announce the server URL as the "http" (non-"https") version. Thanks to everybody involved in making this feature! Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.