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?
Community moderators have prevented the ability to post new answers.
I've just hit the exact same issue. Any update on when this might be available?
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Any status on this? This is a still troublesome.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.