The plan is not configured for remote triggering.

[lance_lyons]

Hi,  We are trying to work on a remote triggering approach on some builds calling our bamboo rest api.

We have a build which as a stage and some tasks.  From the bamboo build table, the fullkey's for this build are show below.

FULL_KEY    BUILDKEY

SERGIT-OBTS    OBTS

SERGIT-OBTS-GMDB    GMDB

SERGIT-OBTS-JOB1    JOB1

I have tried

https://bamboo.companyname.com/api/rest/updateAndBuild.action?planKey=SERGIT-OBTS

https://bamboo.companyname.com/api/rest/updateAndBuild.action?buildKey=SERGIT-OBTS

and several other variations.

I always get    The plan "the full name of the plan that it looked up" is not configured for remote triggering.

what am I doing wrong?

Is there some global setting to turn on remote triggering?

[rsperafico]

Hello Lance Lyons,

I would suggestion you on using any of the following URLs to trigger build(s) in Bamboo:

http://localhost:8085/api/rest/updateAndBuild.action?buildKey=PROJ-PLAN
 
# Requirements
- Repository configured for the PROJ-PLAN (Plan configuration >> Repositories)
- Remote Trigger (Plan configuration >> Triggers)
 
# Behaviour
- Bamboo will check whether there are changes in the repository setup, checking for changes against all branches within PROJ-PLAN (i.e PROJ-PLAN0, PROJ-PLAN1...) If changes are found in any of the branches, Bamboo will trigger a build against the branch as well
 
# Notes
- Cannot be used with IPv6

 The method above will increase load in Bamboo whereas the method below will be triggering a specific build.

# https://docs.atlassian.com/bamboo/REST/5.14.3.1/#d2e578
curl -u USERNAME -X POST 'http://localhost:8085/rest/api/latest/queue/PROJ-PLAN'
 
# Behaviour
- Bamboo will trigger the build specified in the URL only. If you want to trigger a particular branch, you can update the url to 'http://localhost:8085/rest/api/latest/queue/PROJ-PLAN123' where 123 is the referred branch in your Plan.

 Information above extracted from https://answers.atlassian.com/questions/45835511
—

Kind regards,

Rafael
Atlassian

[lance_lyons]

It turns out that in order to do remotely triggered builds you have to set up a repository triggered build under the plans triggers and set the IP address where the call will come from.