Install and Configure Atlassian Bamboo on Ubuntu Linux

Last reviewed: September 2026

Atlassian Bamboo is a continuous integration and delivery server that coordinates build plans, tests, artifacts, deployment projects and build agents. This guide focuses on a production-conscious Ubuntu installation without hardcoding a Bamboo or Java version that may become unsupported.

Before installation#

• Choose a Bamboo release covered by your organization’s support and licensing plan.
• Check the supported platforms page for the exact Java, database, browser and operating-system requirements of that release.
• Use an external supported database for production.
• Plan HTTPS, DNS, reverse proxy and firewall rules before onboarding users.
• Create backup and recovery procedures for both Bamboo home and the database.
• Estimate local and remote agent capacity for expected build concurrency.

Directory layout#

Keep the application installation and Bamboo home in separate directories. Upgrades replace application files while preserving the home directory and database.

Create a dedicated service account#

Install a supported Java runtime#

Install the Java version listed for the selected Bamboo release. Do not assume an older article’s Java version remains supported.

Download and extract Bamboo#

1. Download the Linux archive from Atlassian’s official distribution channel.
2. Verify the expected filename, checksum or signature when provided.
3. Copy the archive to the server through an approved administrative path.
4. Extract it into a versioned directory under /opt/atlassian.
5. Point a stable current symlink to the active version.
6. Set ownership to the dedicated Bamboo service account.

Configure Bamboo home#

Edit the bamboo-init.properties file inside the extracted application and set bamboo.home to the dedicated application-data directory.

Configure the database#

• Create a dedicated database and database account.
• Use a strong secret stored outside source control.
• Grant only the privileges required by Bamboo.
• Configure supported encoding, collation and connection parameters.
• Allow network connections only between Bamboo and the database.
• Include the database in tested backup and restore procedures.

First controlled start#

Run Bamboo as the service account during initial validation. Confirm that the process writes only to intended paths and binds to the expected application port.

Complete the setup wizard#

1. Open the Bamboo URL through the restricted administrative network path.
2. Apply the valid license.
3. Connect the supported external database.
4. Create the initial administrator account.
5. Configure the base URL and outbound mail.
6. Review artifact, build and agent directories.
7. Verify authentication and authorization before inviting users.

Run Bamboo as a service#

Use systemd or the operating system’s standard service manager. Match the executable paths and process behavior to the installed Bamboo release, then test stop, start, restart and boot behavior before production use.

1. Reload the service manager after creating the unit.
2. Enable Bamboo to start automatically if required.
3. Start Bamboo and verify its service status.
4. Review service logs for startup errors.
5. Test a controlled restart and server reboot.

Reverse proxy and HTTPS#

• Terminate TLS with a trusted certificate.
• Set the public base URL consistently.
• Forward the original scheme and host headers.
• Restrict the application port from direct public access.
• Configure request-size and timeout limits for expected artifacts.
• Test redirects, callbacks, agents and repository integrations after proxy changes.

Build agents#

Use agents to isolate build workloads from the Bamboo server. Separate agents by trust level, operating system, toolchain and network access. Avoid granting broad cloud or production credentials to general-purpose agents.

Security checklist#

• Integrate with the approved identity provider when supported.
• Apply least-privilege global and project permissions.
• Store repository and deployment credentials in protected Bamboo credential facilities.
• Patch Bamboo, Java and plugins through a tested change process.
• Remove unused integrations and agent capabilities.
• Restrict administrative access and audit configuration changes.
• Scan build artifacts and protect deployment approvals.

Backup and recovery#

• Back up the external database consistently.
• Protect Bamboo home and encryption-related configuration.
• Record application, Java and plugin versions.
• Exclude disposable caches only when documented by the selected release.
• Test restoration on an isolated server.
• Keep a rollback plan for upgrades and database changes.

Common troubleshooting#

• Bamboo will not start: verify Java compatibility, file ownership, Bamboo home and service logs.
• Setup cannot connect to the database: check driver support, credentials, network rules and database configuration.
• Reverse-proxy redirect loop: verify the public base URL and forwarded protocol headers.
• Agent remains offline: inspect authentication, capabilities, Java, time and network connectivity.
• Build cannot find a tool: confirm agent capabilities, PATH and executable permissions.
• Upgrade fails: restore the pre-upgrade snapshot only according to the documented rollback plan.

Official references#

Bamboo installation and upgrade documentation

Bamboo supported platforms