Migrate 'Jenkins' Hook to webhook

I am trying to migrate my Jenkins Hook to the new webhook and have run into a snag.

After each CI build we are tagging our code, With the git plugin for Jenkins, with a unique version number which matches the NUGET package version with each build for trace-ability.

When I remove the Jenkins Hook and create it as a webhook, the tagging of the code now causes the repository push to trigger, thus causing an endless cycle of builds. 

I had to remove the webhook and return to the Jenkins Service as it is now called.

Are there any plans to allow the webhook to trigger with a code push and not trigger with a tag only push?

2 answers

Hi Bruce,

Thanks for trying out the new webhooks. That is a reasonable request and will be generally useful. I am creating an issue in our JIRA to track it. I will keep you updated on the progress.

Kind Regards,

Brian Edwards

Any status on this?  This is a still troublesome.

I've just hit the exact same issue. Any update on when this might be available?

Suggest an answer

Log in or Join to answer
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...

631 views 0 4
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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot