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?
