Changing the JIRA-Bamboo integration cache settings in Bamboo

If you have integrated Bamboo with JIRA, you may wish to change the JIRA-Bamboo integration cache settings to tweak performance. Bamboo caches JIRA data when it retrieves issue data, to prevent repeat calls to JIRA from degrading performance.

Bamboo caches the following JIRA information:

• Issue Details — a summary representation of the JIRA information (including the Type, Status and Summary) for each issue is stored by Bamboo.
• Issue Meta-Data — the reference information (e.g. Status codes) used to translate the summary representation of JIRA information into display values is also cached by Bamboo.

The caching behaviour for the Issue Details and Issue Meta-Data is described below:

• Issue Details — Issue Details are usually cached by Bamboo when the issue is first accessed by Bamboo (although some background synchronisation of data does occur). The cached data is stored for 86,400,000 ms (i.e. 24 hours) before it is cleared.
• Issue Meta-Data — Issue Meta-Data is cached in the background by synchronisation tasks, rather than waiting until the information is first accessed. The cached data is stored for 864,000,000 ms (i.e. approximately 10 days).

This caching behaviour is designed to optimise system performance against the currency of information, but if you wish to change the default behaviour (e.g. you need to keep up to date with rapidly changing JIRA data and can tolerate reduced Bamboo performance) you can do so by modifying the following timeout values via the system properties:

• bamboo.jira.issueCache.timeToLive
• bamboo.jira.metaDataCache.timeToLive

You can do this by adding the timeout values as command line parameters when starting Bamboo.
e.g.
-Dbamboo.jira.issueCache.timeToLive=86400000
-Dbamboo.jira.metaDataCache.timeToLive=864000000