[Bamboo Knowledge Base]
The information on this page describes how to find important Bamboo directories and files.
On this page:
Bamboo server installation directory
When you installed your Bamboo server, you specified the location for the Bamboo installation directory — this is the directory where the Bamboo application files are installed. (The default location depends on your operating system: Windows, Unix/Linux, Solaris or Mac OS.)
atlassian-bamboo/WEB-INF/classes/bamboo-init.properties | This file tells Bamboo where to find the Bamboo home directory. The location of this directory is specified by the Bamboo administrator as described in the Bamboo installation guide, and can be viewed as described in Viewing Bamboo's System Information. |
bin/start-bamboo.sh | This is the startup file for Bamboo under Unix/Linux, Solaris and Mac OS. |
bin\start-bamboo.bat | This is the startup file for the Bamboo under Windows. |
scripts/Triggers | This directory contains operational scripts (used when configuring the repository to trigger a Bamboo build). |
logs/* | This directory contains logs unless you have used the Installer for Windows. (Note: The Bamboo server logs are written to the root of the installation directory. Build logs are stored in the <BambooHome>/xml-data/builds/ sub-directories.) If you used the Installer for Windows, log files will be located at %USERPROFILE%\bamboo.log. For Bamboo running as a Windows service it can be found at %WINDIR%\System32\Config\systemprofile\bamboo.log. |
| This directory is used when deploying Bamboo add-ons. It also contains other libraries required by Bamboo. |
| This is Bamboo's logging configuration file. Also the logging can be configured from the Bamboo UI by navigating to Administration -> Log Settings page, but the changes made on that page will be reverted by a Bamboo restart; however, changes made in the log4j.properties file will stay even if Bamboo gets restarted. |
Bamboo server home directory
When you installed your Bamboo server, you specified the location for the Bamboo home directory — This is the directory where your Bamboo configuration data and build results are stored. (The default location depends on your operating system: Windows, Unix/Linux, Solaris or Mac OS.) This directory can grow quite large when managing large quantities of plans and builds.
artifacts/PLAN_KEY/shared/build-BUILD_NUMBER/ | This is a folder shared by all the stages of a certain plan. Stages will place Artifacts here so that other stages from the same plan can have access to them. The BUILD_NUMBER will always have a minimum of 5 digits, having the number completed with zeros when necessary. For instance, for build "42" the number will be "00042". |
bamboo.cfg.xml | This is Bamboo's core configuration file. It includes the configuration information for connecting to Bamboo's database. |
xml-data/ | This directory contains all files relating to source repositories and build results. |
xml-data/build-dir/JOB_KEY | This is known as the Working Directory. This is where Bamboo temporarily puts the checked-out files it is building. The location of this directory was specified using the Setup Wizard, can be viewed as described in Viewing Bamboo's System Information, and can be changed as described in Specifying Bamboo's Working Directory. |
xml-data/builds/ | This is known as the Build Directory. This is where Bamboo stores build results (note that they will be deleted as described in Configuring global build results expiry). The location of this directory was specified using the Setup Wizard, and can be viewed as described in Viewing Bamboo's System Information. Its contents can be backed up as per Exporting data for backup. |
xml-data/builds/JOB_KEY/results | Contains the build results for all the builds belonging to the JOB_KEY plan. Each build result is an individual XML file. Do not edit these files or the corresponding information in the database may become corrupt. |
xml-data/builds/JOB_KEY/download-data | Contains the logs for each build belonging to the JOB_KEY plan. |
xml-data/configuration/ | This is known as the Configuration Directory. It contains server-wide configuration information. The location of this directory was specified via the Setup Wizard, and can be viewed as described in Viewing Bamboo's System Information. Its contents can be backed up as per Exporting data for backup. |
database/ | This directory contains Bamboo's embedded HSQL database. The database contains plan configurations and some build results data. This directory is not present if an external database is used instead of the embedded HSQL.
|
index/ | This directory contains the build results index. Removing or modifying files in this directory may corrupt build history. Rebuilding the search index from Bamboo's global administration screen (see Optimising or re-indexing data) will completely regenerate the contents of this directory. |
logs/* | This directory contains logs unless you have used the Installer for Windows. (Note: The Bamboo server logs are written to the root of the installation directory. Build logs are stored in the |
HSQL is Bamboo agent home directory
When you installed your remote agents (if any), you specified the location for the Agent home directory — this is the directory where the agent's configuration data is stored. The default name of this directory is bamboo-agent-home. (The default location depends on your operating system: Windows, Unix/Linux, Solaris or Mac OS.) This directory can grow quite large when managing large numbers of plans and builds.
The contents of the agent home directory are:
bamboo-agent.cfg.xml | This contains configuration information about this remote agent. Most notably, it stores the agent id, which gets generated the first time this agent connects to the Bamboo server. |
xml-data/build-dir/ | This is where the agent will check out the files and perform builds (similar to the Bamboo server's xml-data/build-dir/ directory) |
Overview
Content Tools
Apps
Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.