When you launch Bamboo for the first time, the Bamboo setup wizard will display. The wizard will lead you through the Bamboo settings that you need to configure before you can start using it.
Before you begin
If you are currently using Atlassian's Crowd with Bamboo and wish to import existing data into Bamboo (see Step 5. Starting Data below), you will need to disable Crowd before starting the Setup Wizard. To do this, go to Administration > User Repositories (under 'Security') and choose Local users and groups.
You can then re-enable Crowd and restart Bamboo at the completion of the Setup Wizard.
Step 1. License Details and Setup Method
You must have a valid Bamboo license (evaluation or commercial) to use Bamboo. You can generate your own Bamboo evaluation license from your MyAtlassian self-service account here. If you have any problems with this, please email sales.
Once you have entered a valid license key, you can choose which setup method you prefer for your Bamboo installation:
Express Installation — we recommend that you choose this method if you are evaluating or demonstrating Bamboo.
- The 'Express Installation' method requires only a minimum of configuration information. It sets up Bamboo with default settings and an embedded database (HSQL).
- If you choose the 'Express Installation' method you can skip to Step 6. Set Up Administrator User below.
On this page:
Custom Installation — we recommend that you choose this method if you are setting up a production instance of Bamboo.
- The 'Custom Installation' method takes longer, but allows you to configure Bamboo with an external database, customise the default settings, and/or initialise the server with your own data.
- If you choose, the 'Custom Installation' method, proceed to Step 2. General Configuration below.
Screenshot: License Details and Setup Method
Step 2. General Configuration
This step applies to the 'Custom Installation' method only.
On this page you specify a number of Bamboo server settings, such as the address of the server, where data is stored and the message broker used to communicate with remote agents.
You may find it simplest to keep the default settings for the three directory settings, in the table. For more information please see Locating important directories and files.
| Setting | Details |
|---|---|
| Name | See Specifying Bamboo's Title |
| Base URL | See Specifying Bamboo's URL |
| Configuration Directory | The location for Bamboo configuration files. |
| Build Data Directory | The location for Bamboo project data files. |
| Build Working Directory | The location of project files checked out from source control. |
| Broker URL | Only visible if you are permitted remote agents under your Bamboo license. The URL of the embedded messaging broker that Bamboo sets up to communicate with its remote build agents. This URL will be written to
|
Screenshot: General Configuration
Step 3. Choose a Database Configuration
This step applies to the 'Custom Installation' method only.
Picking a database configuration is an important choice. If you pick the 'Embedded Database' configuration, you do not have to set up a database. However, the embedded HSQL database is only suitable for evaluation purposes. You will need to move to an external database, if you decide to deploy Bamboo in production at a later stage (as described in Moving your Bamboo data to a different database).
Choose one of the following:
- Embedded Database — Choose this for quick and easy first-time installation of Bamboo. This option is suitable for evaluation purposes only. Skip to Step 5. Starting Data.
- External Database — Choose this if you wish to use an external database. Proceed to Step 4. Database Configuration below.
Screenshot: Choose a Database Configuration
Step 4. Database Configuration
This step applies to the 'Custom Installation' method only.
If you selected 'External Database' in Step 3, you will need to provide the configuration details for your database. Please see Connecting Bamboo to an external database for further instructions.
Screenshot: Database Configuration
Step 5. Starting Data
This step applies to the 'Custom Installation' method only.
Screenshot: Starting Data
On this page you specify how Bamboo will populate the 'home directory' that you set up when you installed Bamboo.
Choose one of the following:
- Create new Bamboo home — choose this if you are performing a normal installation or upgrade.
- Import existing data — only choose this under exceptional circumstances, e.g. if you are connecting Bamboo to a different database, or moving your pre-existing Bamboo installation to a different server. Avoid importing backups from different versions of Bamboo.
Step 6. Set Up Administrator User
The final step of the setup wizard is to enter the details of the first registered user for the Bamboo system. This user will have global administrative privileges over the entire installation of Bamboo and should not be removed.
Once you have entered the details for your administrator user, click Finish. The Bamboo dashboard will be displayed.
Congratulations, you have successfully set up Bamboo!
Screenshot: Set Up Administrator User
6 Comments
Anonymous
Jun 29, 2012Hi I have problem with the last step. If I click to the finish button so I get the error message.
Do you have idea?
I run help of tomcat6.
Anonymous
Feb 20, 2013This could be a permissions issue. Please check the correct ownership for bamboo home directory.
Lorenzo
Jul 14, 2013This also happens when tomcat is running and you are copying a rather long war file in its war directory. I had this too a lot of times. It appears that tomcat detects the presence of a new app and tries to unzip it while copying isn't finished yet hence it thinks the zip is corrupt. Shut down tomcat, copy the war, when done, restart it. If that was really the issue it should be gone now.
Lorenzo
Jul 14, 2013Installing Bamboo on OSX 10.8.4 now. It created the DB tables and all and now it has been irritating my CPU's for the past 15 minutes, driving all 4 of them towards 70% average. Something says this isn't particularly right...
EDIT: It appeared to be shortage in PermGenSpace. Updated tomcat catalina.sh and problem solved. I then got an Slf4j LoggerFactory ClassNotFoundException.... Copied slf4j libs in lib dir of tomcat...
Igor Cicimov
Sept 16, 2013Hi all,
I've juts installed Bamboo 5.1.0 on Ubuntu 12.04.2 LTS. I've setup PostgreSQL 9.1 as external database but during the initial setup I'm getting the following errors:
2013-09-16 09:24:22 EST STATEMENT: drop table TRUSTED_APPS_IPS
2013-09-16 09:24:22 EST ERROR: table "password_reset_token" does not exist
2013-09-16 09:24:22 EST STATEMENT: drop table password_reset_token
2013-09-16 09:24:22 EST ERROR: table "deployment_version_status" does not exist
2013-09-16 09:24:22 EST STATEMENT: drop table DEPLOYMENT_VERSION_STATUS
2013-09-16 09:24:22 EST ERROR: table "deployment_version_jira_issue" does not exist
2013-09-16 09:24:22 EST STATEMENT: drop table DEPLOYMENT_VERSION_JIRA_ISSUE
2013-09-16 09:24:22 EST ERROR: table "brs_artifact_link" does not exist
2013-09-16 09:24:22 EST STATEMENT: drop table BRS_ARTIFACT_LINK
2013-09-16 09:24:22 EST ERROR: table "deployment_project_item_ba" does not exist
2013-09-16 09:24:22 EST STATEMENT: drop table DEPLOYMENT_PROJECT_ITEM_BA
2013-09-16 09:24:22 EST ERROR: table "artifact" does not exist
2013-09-16 09:24:22 EST STATEMENT: drop table ARTIFACT
2013-09-16 09:24:22 EST ERROR: table "hibernate_unique_key" does not exist
2013-09-16 09:24:22 EST STATEMENT: drop table hibernate_unique_key
2013-09-16 09:24:23 EST ERROR: could not read block 43 in file "base/63394/11787": read only 0 of 8192 bytes
2013-09-16 09:24:23 EST STATEMENT: alter table DEPLOYMENT_RESULT add constraint FKB7ACDAD7A248FEE7 foreign key (ENVIRONMENT_ID) references DEPLOYMENT_ENVIRONMENT
2013-09-16 09:24:23 EST ERROR: could not read block 43 in file "base/63394/11787": read only 0 of 8192 bytes
2013-09-16 09:24:23 EST STATEMENT: alter table DEPLOYMENT_RESULT add constraint FKB7ACDAD7F4F36A02 foreign key (VERSION_ID) references DEPLOYMENT_VERSION
2013-09-16 09:24:23 EST ERROR: could not read block 43 in file "base/63394/11787": read only 0 of 8192 bytes
2013-09-16 09:24:23 EST STATEMENT: alter table DEPLOYMENT_RESULT add constraint FKB7ACDAD7E3B5B062 foreign key (VARIABLE_CONTEXT_BASELINE_ID) references VARIABLE_CONTEXT_BASELINE
2013-09-16 09:24:23 EST ERROR: could not read block 43 in file "base/63394/11787": read only 0 of 8192 bytes
2013-09-16 09:24:23 EST STATEMENT: alter table DEPLOYMENT_VERSION_ITEM add constraint FKEC5E1747BD9BBC foreign key (DEPLOYMENT_VERSION_ID) references DEPLOYMENT_VERSION
2013-09-16 09:24:23 EST ERROR: could not read block 43 in file "base/63394/11787": read only 0 of 8192 bytes
2013-09-16 09:24:23 EST STATEMENT: alter table ELASTIC_SCHEDULE add constraint FK1C6B30E1581FB731 foreign key (ELASTIC_IMAGE) references ELASTIC_IMAGE
2013-09-16 09:24:23 EST ERROR: could not read block 43 in file "base/63394/11787": read only 0 of 8192 bytes
2013-09-16 09:24:23 EST STATEMENT: alter table TEST_CLASS_RESULT add constraint FK3521FF712170166F foreign key (TEST_CLASS_ID) references TEST_CLASS
2013-09-16 09:24:23 EST ERROR: could not read block 43 in file "base/63394/11787": read only 0 of 8192 bytes
.
.
and so on, lots of errors about not being able to read the specific database file and thus failing creating constraints. And the database file is really empty:
root@server:/opt/atlassian-bamboo-5.1.0# ls -l /var/lib/postgresql/9.1/main/base/63394/11787
-rw------- 1 postgres postgres 0 Sep 16 09:20 /var/lib/postgresql/9.1/main/base/63394/11787
We already have bamboo 4.2.1 running on the same server using the same PostgreSQL 9.1 database, different instance though.
Any ideas why is this failing?
Thanks,
Igor
Mike Smith
Oct 25, 2013Would be nice if the default installation port for Catalina were included in the instructions...if you didn't know where to look for it, how would you start to work on the actual configuration of Bamboo through the UI?
BTW, the default http port is 8085.