Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,361,135
Community Members
 
Community Events
168
Community Groups

Can bamboo plans be triggered via webhook without committing changes?

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?

2 answers

1 vote

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.

0 votes

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

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.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo 9.0 is now available

Hey there, Data Center community! I'm Martyna Wojtas and I am the Product Manager for Bamboo Data Center. I’m excited to share that Bamboo 9.0 is now available. We purpose-built this platform to help...

311 views 0 7
Read article

Atlassian Community Events