Can bamboo plans be triggered via webhook without committing changes?

Question

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?

Mitch Williams · Answer

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.

Alexey Chystoprudov · Answer

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 · Answer

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.