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?
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 ...
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!
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot