Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Can bamboo plans be triggered via webhook without committing changes?

Mitch Williams October 24, 2018

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
Marcin Gardias
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 25, 2018

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

Mitch Williams October 25, 2018

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
Alexey Chystoprudov
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 26, 2018

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

Mitch Williams October 26, 2018

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
AUG Leaders

Atlassian Community Events