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
Next: Root
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.
I would like to always trigger a new run of a bamboo plan in response to a webhook. Other community support questions suggest using the path /rest/triggers/1.0/remote/changeDetection, however this does not run the plan if there are no changes. Furthermore, the entire '/rest/triggers' family of resources seems to be undocumented
Is there another path, or parameters that I can pass to changeDetection to force bamboo to start a build?
Hi, I think what you need is 'queue' resource. POST on that resource queues the build unconditionally (well, sort of, it will queue build if there are no changes but it will still check if you don't exceed concurrency level for the plan and such)
Documentation: https://docs.atlassian.com/atlassian-bamboo/REST/6.6.0/#d2e2977
I agree that POST-ing to the 'queue' resource would have the desired effects, but I believe the 'rest/api' resources require authentication. 'rest/triggers', being webhook endpoints, do not.
In this case, the webhook is originating from bitbucket-server, but I don't see an obvious way for it to authenticate with bamboo.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What kind of events from Bitbucket your build build should react? As I understand it's not commit event. By security reasons it's not safe to allow anyone to trigger any build at your Bamboo instance with anonymous HTTP call, that's why rest/remote/changeDetection checks changes at linked repository
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What kind of events from Bitbucket your build build should react?
pull request creation and potentially related events.
By security reasons it's not safe to allow anyone to trigger any build at your Bamboo instance with anonymous HTTP call, that's why rest/remote/changeDetection checks changes at linked repository
I'm not sure I see much of a distinction between anonymously triggering a build with changeDetection and just queuing a build according to normal rules, but I can understand encouraging a cautious posture.
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.