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
Community Members
Community Events
Community Groups

Is there way view all the triggers for the various plans in a single place?

We would like to see when and what various jobs are expected to run so that we can effectively utilize the resources ( agents ) better by scheduling plans when there are likely to be more free agents. Also helps us plan down times.

2 answers

Hi @Subhi Andrews ,

You can consume a REST API endpoint and review all the CRON jobs Bamboo will be executing next (including builds to be triggered):

# USERNAME, replace with Bamboo Administrator username
# http://localhost:8085/bamboo, replace with Bamboo's Base URL

curl -k -u USERNAME -H "Accept: application/json" \
-X GET http://localhost:8085/bamboo/rest/admin/1.0/scheduler/jobs

As a result, you will find which plans will be executed when having (Scheduled, Single daily run, Repository Polling - Periodically and Scheduled)

"name": "CHAIN:PROJ-PLAN:1",
"groupName": "",
"nextScheduledTime": "2019-03-16T00:00:00.000Z"

And no information on this REST API endpoint for Remote trigger, Bitbucket repository triggers the build when changes are committed.

In case you are looking for more detail information regarding on Build Triggers in Bamboo, you could run a SQL statement against Bamboo's database and XPATH "build_definition-XML_DEFINITION_DATA" to get the trigger set up under Plan configuration >> Trigger tab:

select b.FULL_KEY
from build b
join build_definition bd on b.build_id = bd_build_id

You should find the following in :

<configuration xml:space="preserve">
<name>Repository polling</name>
<value>0 0 0 ? * *</value>

The example above is for Repository Polling - Periodically, so you can notice:

  • <pluginKey />, relates to the type of triggering method available (e.g com.atlassian.bamboo.triggers.atlassian-bamboo-triggers:poll)
  • <triggeringRepositories />, informs to which repository the trigger has been defined
  • repository.change.poll.type, relates to type of Repository Polling selected, in this case PERIODically
  • repository.change.poll.pollingPeriod, what is the interval between triggering events (e.g 1800000 seconds)

As you can notice, it is require some effort in order to get the information you are looking for. I would encourage you on commenting, voting and/or becoming a watcher to As an admin, I would like to review plan(s) triggering so you can receive latest updates.

Kind regards,


Thanks so much for a super helpful and informative post, Rafael! 

I don't see this in the REST API docs and it isn't working for me.

Here's a feature request that might be of interest to those who are reading this. Please vote

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events