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.
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": "repository.change.jobs",
"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
, XPATH_GET_TRIGGER
from build b
join build_definition bd on b.build_id = bd_build_id
where XPATH_TRIGGER_IS_DEFINED;
You should find the following in :
<configuration xml:space="preserve">
...
<triggers>
<defined>true</defined>
<triggerDefinition>
<id>1</id>
<name>Repository polling</name>
<userDescription>p</userDescription>
<isEnabled>true</isEnabled>
<pluginKey>com.atlassian.bamboo.triggers.atlassian-bamboo-triggers:poll</pluginKey>
<triggeringRepositories>5341185</triggeringRepositories>
<config>
<item>
<key>repository.change.poll.pollingPeriod</key>
<value>1800000</value>
</item>
<item>
<key>repository.change.poll.type</key>
<value>PERIOD</value>
</item>
<item>
<key>repository.change.poll.cronExpression</key>
<value>0 0 0 ? * *</value>
</item>
</config>
<conditions>
<item>
<key>custom.triggerrCondition.plansGreen.enabled</key>
<value>false</value>
</item>
</conditions>
</triggerDefinition>
</triggers>
The example above is for Repository Polling - Periodically, so you can notice:
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 https://jira.atlassian.com/browse/BAM-19972 - (REST) As an admin, I would like to review plan(s) triggering so you can receive latest updates.
Kind regards,
Rafael
Thanks so much for a super helpful and informative post, Rafael!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't see this in the REST API docs and it isn't working for me.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Here's a feature request that might be of interest to those who are reading this. Please vote
https://jira.atlassian.com/browse/BAM-21194
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.