Details
-
Suggestion
-
Resolution: Fixed
-
None
-
0
-
2
-
Description
Problem Definition
NAS / NFS for <bamboo-home> is common however our JMS processing doesn't perform well when the jms-store is not on fast, low-latency, local storage.
It would be great to have a property to to change the location of the jms-store so that all of <bamboo-home> can exist on the NAS / NFS, with the exception of the jms-store.
Suggested Solution
- Implement a property that can be configured in the <bamboo-home>/bamboo.cfg.xml to override the default path for the jms-store.
Workaround
- Point <bamboo-home> at local storage in <bamboo-install>/atlassian-bamboo/WEB-INF/classes/bamboo-init.properties
- You will need to move all files and subdirectories that are not covered by the below properties to the local storage location.
- Modify each individual path within <bamboo-home>/bamboo.cfg.xml and point it at the NAS / NFS:
<property name="bamboo.artifacts.directory">${bambooHome}/artifacts</property> <property name="bamboo.config.directory">${bambooHome}/xml-data/configuration</property> <property name="bamboo.project.directory">${bambooHome}/xml-data/builds</property> <property name="bamboo.repository.logs.directory">${bambooHome}/xml-data/repository-specs</property> <property name="buildWorkingDir">${bambooHome}/xml-data/build-dir</property> <property name="daily.backup.dir">${bambooHome}/backups</property> <property name="webwork.multipart.saveDir">${bambooHome}/temp</property>
Notes
The largest directories are usually bamboo.artifacts.directory, bamboo.project.directory, buildWorkingDir and daily.backup.dir.
It is recommended to keep the lucene.index.dir on local storage too:
<property name="lucene.index.dir">${bambooHome}/index</property>