Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Jenkins Trigger build on Bitbucket when merge branch

Hi, I am fairly new to Bitbucket/Jenkins and I am trying to get Jenkins to trigger a build when my branch is merged into master on Bitbucket.

First of all I have successfully been able to integrate my Jenkins with Bitbucket so when I do a push on my branch to Bitbucket via a webhook, it will trigger a build in Jenkins and grab all the files and push to the correct environment. I've noticed in the webhook there is a trigger for Merge however when select this does not trigger a build.

Is there any appropriate plugin for this I can download for Jenkins or any help and advice would be greatly appreciated.


3 answers

1 vote

It is actually a rather typical automation problem which can be implemented with the Better DevOps Automation add-on.

Here is the step-by-step guide. It will just trigger the desired Jenkins build after every change even if that is a merge.

Note that there are other recipes available for more complex automation needs, like running a particular build if the "@build" command is in the commit message:


We're having the same issue here with our BitBucket Cloud server and our Azure-hosted Jenkins server. I have the following setup:

Jenkins 2.164.2
'Build when a change is pushed to BitBucket' checked in Jenkins job (BitBucket Plugin installed)

In the BB repository, added a hook under Settings -> Webhooks:
Title: Jenkins
URL <our jenkins server>/bitbucket-hook/
Status: Active
Request History: Enabled
Triggers: Choose from a list
Pull Request - Merged ticked only

When I merge a pull request, the hook is triggered and 200 response comes back from Jenkins, but no build is triggered:


In Jenkins I get a 'BitBucket Hook Log' tab but it just says 'Polling has not run yet'

One workaround is to create one job per branch. But that is certainly not DRY.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events