How does Bitbucket Webhook to Jenkins know which job will build?

[Roger Myung]

Hello,

I am looking to setup a hook from Bitbucket to Jenkins.  The "Bitbucket Webhook to Jenkins" has the nice display showing which commits have been build, so I'm interested in using it, but I'm not sure how it determines which Jenkins job to build.  If multiple jobs are setup to use the repository, how would the hook know which one to trigger?  In comparison, the Http Request Post Receive Hook defines a specific job to trigger(and the job can be configured with an authentication token. 

Thanks!

[Michael Irwin]

Upon a new commit, new pull request, etc., the Bitbucket plugin sends a notification to Jenkins, using a simple HTTP request.  In the HTTP request contains the repo's clone URL and, based on configuration, the branch(es) and commit hash.  The Jenkins plugin then looks at its job configurations to see what builds have a matching repository URL.  If a match is made, Jenkins schedules a build.