Having a hard time understanding how to get to the payload data in the webhook request triggered by Bitbucket. I can’t find any explanation in the documentation.

The scenario is as follow.

I have created a Jenkins standard job (no pipeline) where I have setup the plugin as described in the documentation and it now appears to work with SSH creds (thanks for the fix mhenschke_atlassian in JENKINS-60492).

In the “Branch Specifier”-field I can “hardcode” the branch/etc I want to build. I intentionally write hardcode since I want to be able to pass that branch specification as an argument in the webhook call (or having access to the payload that comes with the request in order to  use that when determining what to build).

See https://confluence.atlassian.com/bitbucketserver/event-payload-938025882.html 

If I don’t specify any branch at all then loads of existing branches starts to build (which is what’s expected I think) 

What is it that I have misunderstood here? 

Regards

– Kent