Supported platforms

CPU:

Evaluation: 1 core 
Production: 2+ cores

Memory:

3GB+

Good to know:

• You'll need at least 3GB available memory. We recommend 1GB for Bitbucket Server and an additional 2GB to support Git operations. 
• Your specific hardware requirements will depend on the number and frequency of Git operations and the number of active users. See Scaling Bitbucket Server for more information. 

 Linux

 Microsoft Windows (up to 500 users)

 Apple macOS

Known issues:

• Microsoft Windows is not supported for Bitbucket Data Center / 500+ Enterprise tiers.
• You should not use Windows Resilient File System (ReFS) as NTFS is required.
• Apple macOS is evaluation only, macOS cannot be used for production deployment.

Good to know:

• In production environments Bitbucket Server should be run from a dedicated user account.

 Amazon Web Services (AWS)

Known issues:

• You can't use Amazon Elastic File System (EFS) for Bitbucket's shared home directory.

Good to know:

• See Recommendations for running Bitbucket in AWS for more information.

Oracle Java:

  1.8u65+

OpenJDK:

 1.8u65+ 

 1.8u40+

 1.8u0 - 1.8u20

Known issues:

You should not use Bitbucket Server with:

• OpenJDK >= 1.8u25 and < 1.8u40 due to a severe bug. See Bug 1167153 (this is fixed in 1.8u40).
• OpenJDK 1.8u51 and 1.8u60 due to LDAP issues. See CWD-4444.

Good to know:

• The Bitbucket Server installer will install a supported version of the Oracle Java JRE which is only available to Bitbucket Server, if necessary. See Running the Bitbucket Server installer.
• If you choose to pre-install a JRE, we recommend using Oracle JRE 8, which you can download from the Oracle website.
• We recommend Java 1.8.0u40+ to avoid critical defects in older versions. If you are terminating SSL at Tomcat there is a known Java bug that has been fixed in version 1.8.0u51. Alternatively, you can continue using 1.8u40+ with the addition of a JVM flag. Further details: Application crashes due to 'Internal Error (sharedRuntime.cpp:833)' caused by Java 8 bug.
• For OpenJDK, download and install instructions for Linux flavors at http://openjdk.java.net/install/.
• Pre-installed Java on some AWS EC2 Linux instances might be installed with a subset of features. See SSH server fails to start on AWS EC 2 instance  for more information.

PostgreSQL

 9.4 - 9.6

 9.3.6+

  9.2

Known Issues:

Connecting Bitbucket Server to PostgreSQL

PostgreSQL 9.3 versions prior to 9.3.6 (9.3.0 – 9.3.5) contain a bug that is known to cause crashes. (See PostgreSQL segmentation fault after upgrading to Bitbucket 4.11 and up)

MySQL (Bitbucket Server only)

 5.7.9+

 5.6.16+

 5.5.x

 MariaDB 10.2.6+

 MariaDB 10.1.8+

 MariaDB 10.0.10+ 

 MariaDB 5.5

Known issues:

MySQL, while supported by Bitbucket Server, is currently not recommended, especially for larger instances, due to inherent performance and deadlock issues that occur in this database engine under heavy load.

See Connecting Bitbucket Server to MySQL for more details and http://dev.mysql.com/doc/refman/5.0/en/innodb-deadlocks.html for some general information on deadlock issues.

You should not use Bitbucket Server with the following:

• MySQL 5.6.15 and earlier: due to bugs in its query optimizer (#68424, #69005). See Connecting Bitbucket Server to MySQL for more information.
• MySQL 5.7.0 - 5.7.8

Do not use MySQL in Bitbucket Data Center.

Microsoft SQL Server / Microsoft SQL Server Express

 2012 - 2016

Oracle:

12c

H2 (bundled):

   Bitbucket Server, evaluation only

  Bitbucket Mirror

HSQLDB (bundled):

Bitbucket Server only, evaluation only
Deprecated

Known Issues:

MS SQL:

Connecting Bitbucket Server to SQL Server

• Named Instances: If you have a named instance on your server, it is not possible to migrate from the internal database to a named instance of SQL Server using the UI procedure. You will need to manually edit the bitbucket.properties file as described on the Connecting to named instances in SQL Server from Bitbucket Server Knowledge Base article.

  H2:

• H2 is bundled with Bitbucket Server for evaluation use only.
• H2 can be used with Bitbucket Data Center mirrors in production.

HSQLDB:

• Please see connecting Bitbucket Server to an external database.
• HSQLDB is not supported in Bitbucket Data Center.
• HSQLDB support was deprecated as of Bitbucket Server 4.0+. New Bitbucket Server installs will bundle and use H2 as the default database for evaluation purposes.

Git – server

 2.14+

 2.13+

 2.12+ (except 2.12.2 on Windows)*

 2.11+

 2.10+

 2.9+ 

 2.8+ *

 2.7+ *

 2.6+ *

 2.5+ *

 2.4+ *

 2.3+ *

 2.2+ *

Git – server

We recommend using the most recent supported version of Git on both the Bitbucket Server instance and clients where possible, subject to the following notes and exceptions:

• The version of Git installed on machines that interact with Bitbucket Server must be compatible with the version of Git installed for use by the Bitbucket Server instance.
• Do not use CygwinGit on Windows servers, regardless of version.
•  Git 2.2.x - 2.4.0 have some performance issues when interacting with NFS. These versions cannot be used for Bitbucket Data Center or for Bitbucket Server installations that use NFS mounts for the home directory.
• Git for Windows 2.12.2 has a regression in git status which causes editing files to fail. The regression has been fixed, and the fix was included in Git for Windows 2.12.3.
• BSERV-9673 - File editing fails using Git for Windows 2.12.2 CLOSED
• Git 2.2.x - 2.8.x If using mixed line modes, it is recommended to use a version greater than or equal to 2.9.4 as mixed line modes can cause issues with merging and creating pull requests.
  

The table below lists the versions of Git that have been specifically tested against the Bitbucket Server 5.5.x releases.

Git – client

 1.8.4.3
 1.6.6+

Or where Git LFS is used 1.8.2+

Git LFS - client

 1.1.0+

Git – client  

• A bug was fixed in Git version 1.8.4.3 that prevented http push proxying from working. 

Perl

5.8.8+

Elasticsearch

2.3.1 - 2.3.5

Good to know:

• Perl is usually provided automatically with Git