Bitbucket cloud webhooks no longer exclude TAG pushes

I am having issues with the webhook which notifies on repo:push.  Our CI process will TAG the commit used for the build as a post deployment task.  This push of tags will then trigger a new build, which is the undesired behavior. 

Our CI us Jenkins, I am using pipelines. I have configured Jenkins 'Polling ignores commits with certain messages' as well as 'Polling ignored commits from certain users'.  Most of the reading I have done indicate these settings have no impact when using the Bitbucket cloud webhook.  

Prior to September 17, 2017, pushing a TAG to Bitbucket did not trigger a new build.  My assumption is the feature to enable builds to be triggered on tagging was either 'fixed' or 'enabled'.  So how can this be prevented?

0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 06, 2018 in Bitbucket

Upgrade Best Practices

Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...

1,944 views 7 10
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