PostgreSQL - Scheduled (v5.8+)
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Product | Version | Database | Documentation reference |
---|---|---|---|
Bamboo | v5.8.x, v5.9.x, v5.10.x, v5.11.x, v5.12.x, v5.13.x | PostgreSQL | Cron-based scheduling |
Lets find out how to get Bamboo's repository scheduled trigger values from PostgreSQL database along with updating those values.
Get repository scheduled trigger
/*
* Bamboo version: 5.8+
* Database: PostgreSQL
* Triggers: 'Scheduled'
*/
select B.FULL_KEY as PLAN_KEY,
B.TITLE as BRANCH,
VL.PLUGIN_KEY as REPOSITORY_TYPE,
unnest(xpath
('//triggerDefinition/pluginKey[text()="com.atlassian.bamboo.triggers.atlassian-bamboo-triggers:schedule"]/../config/item/key[text()="repository.change.schedule.cronExpression"]/../value/text()', BD.XML_DEFINITION_DATA::xml)
) as FREQUENCY,
BD.BUILD_DEFINITION_ID as BUILD_DEFINITION_ID
from VCS_LOCATION as VL
join PLAN_VCS_LOCATION as PVL
on PVL.VCS_LOCATION_ID = VL.VCS_LOCATION_ID
join BUILD as B
on PVL.PLAN_ID = B.BUILD_ID
join BUILD_DEFINITION as BD
on B.BUILD_ID = BD.BUILD_ID
where B.SUSPENDED_FROM_BUILDING = false
order by PLAN_KEY, BRANCH
What expect from query above:
PLAN_KEY | TITLE | SCHEDULED | BUILD_DEFINITION_ID |
---|---|---|---|
REP-GIT | Git | 0 0 12 ? * * | 425985 |
REP-SUB | Subversion | 0 0 13 ? * * | 451238 |