As of the security fix in 2.8.4 the build status notifications stopped propagating to our bitbucket server.
It might be something to do with clone links, our repo is configured to only allow ssh clone, so this code fragment seems to not set the base url as it is restricted by the http check
I think, I could create a PR for this but need to know if we should fallback to the "self" link or try to build a base url from the SSH one. If SSH one should we force it to be SSL?
As of the security fix in 2.8.4 the build status notifications stopped propagating to our bitbucket server.
It might be something to do with clone links, our repo is configured to only allow ssh clone, so this code fragment seems to not set the base url as it is restricted by the![image](https://github.com/jenkinsci/bitbucket-push-and-pull-request-plugin/assets/25044236/5813e17b-6750-40e0-aedb-8b0f73eb5213)
http
checkRelevant part of hook payload: