You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
The easiest way to achieve this would probably be the Jenkins Generic Webhook Trigger Plugin.
Once you have configured an inbound webhook trigger in Jenkins, you need to invoke it somehow. As is, the various curl based examples there could all be executed via Bamboo's Script task.
If you are wondering why a webhook is not yet amongst the supported Bamboo notification recipient types, you are not alone - please watch and vote for the following issue to further increase Atlassian's priority for this long missing and highly requested feature:
If you happen to use AWS, you could also work around the missing webhook notification type via the flexible Automate with AWS notification recipient in our (commercial) Automation with AWS (Bamboo) app, which offers various remote actions such as Invoke Lambda Function, which could then trigger the Jenkins webhook in turn.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.