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


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. 


1 answer

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.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 07, 2019 in Marketplace Apps

A Timeless Love Story

It started as any story starts, on a normal, rainy day.   Admin meets App, and her name was Klok2, and like any first relationship we were both trying to make it work but neither one knew what...

463 views 8 27
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you