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
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

2,026 views 1 5
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