Supported platforms details

Supported platforms

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

Hardware

  • As well as the memory allocated for Tomcat (768MB is the default configuration and suitable for most uses), additional memory and CPU capacity is required to support Git operations. We recommend that you use a server with at least 2GB of available memory.
  • The hardware requirements for a full production deployment depend on the number and frequency of Git operations and the number of active users. See Scaling Bitbucket Server for further discussion and for details of how memory is allocated for Bitbucket Server and Git.
  • Amazon Web Services (AWS)
    See Recommendations for running Bitbucket Server in AWS if you're running Bitbucket Server on AWS

Operating systems

  • Bitbucket Server is a pure Java application and should run on any platform, provided all the Java requirements are satisfied.
  • In production environments Bitbucket Server should be run from a dedicated user account.
  • (error) Apple Mac OS X is not supported for production deployment.
  • (error) Microsoft Windows is not supported for 500+ Enterprise tiers.

Java

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 EC2 instance for more information.

Databases

HSQLDB

  • Please see connecting Bitbucket Server to an external database.
  • HSQLDB is bundled with Bitbucket Server, and is only intended for evaluation use.
  • (error) HSQLDB is not supported in Bitbucket Data Center.
  • (warning) HSQLDB support is deprecated as of Bitbucket Server 4.0+. New Bitbucket Server installs will bundle and use H2 as the default database for evaluation purposes.

MySQL

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.

Affected systems may experience slow response times, deadlock errors and in extreme cases errors due to running out of database connections. These issues are intrinsic to MySQL (no other database engine supported by Bitbucket Server shares this behavior) and are due to the way MySQL performs row-level locking in transactions. See http://dev.mysql.com/doc/refman/5.0/en/innodb-deadlocks.html for some general information on this.

Bitbucket Server does its best to work around the MySQL behavior - see issues STASH-4517, STASH-4701 and others, for example. But under very heavy load you will generally get better performance with any of the other database engines supported by Bitbucket Server (such as PostgreSQL, which is also freely available) than you will with MySQL.

  • MariaDB 10.1 releases are still classed as betas and are not supported
  • (error) MySQL 5.6.15 and earlier: Note that Bitbucket Server does not support versions of MySQL 5.6 earlier than 5.6.16 at all, because of bugs in its query optimizer (#68424, #69005). See Connecting Bitbucket Server to MySQL for more information.
  • (error) MySQL 5.7+ is not supported.
  • (error) MySQL is not supported at all in Bitbucket Data Center.

DVCS

Git - server

In general, we recommend using the most recent version of Git on both the Bitbucket Server instance and clients, where possible, and 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.
  • (error) Cygwin Git is not supported for use on Windows servers, regardless of version.
  • (error) Git 1.8.3.x has some performance regressions which may cause problems in Bitbucket Server with large repositories.
  • (error) Git 1.8.4.3 is not supported due to a critical bug in how symbolic refs are handled which breaks pushing and pulling for repositories with pull requests. (Details)
    STASH-4101 - Getting issue details... STATUS
  • (error) Git 2.0.2 and 2.0.3 are not supported due to a critical bug in git diff-tree which breaks Bitbucket Server's commit page. (Details)
    STASH-5052 - Getting issue details... STATUS
  • Git 2.2.x - 2.4.0 have some performance issues when interacting with NFS. Hence, these versions are currently not supported for Bitbucket Data Center or for Bitbucket Server installations that use NFS mounts for the home directory (Details)

[Security vulnerability CVE-2016-2324 & CVE-2016-2315] affects multiple Git versions. Both server and client Git installations should be updated to a patched maintenance version: 2.4.11, 2.5.5, 2.6.6 or 2.7.4 or newer. For instructions see Installing and upgrading Git.

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

LinuxWindows

2.6.0
2.5.5
2.4.11
2.3.8
2.2.3
2.1.4
2.0.5

2.5.2
2.4.6
2.3.7.1

1.9.5
1.8.0.3
1.8.1.5  
1.8.2.3  
1.8.3.4  
1.8.4.5  
1.8.5.6

1.9.5.1
1.8.0
1.8.1.2  
1.8.3      
1.8.4      
1.8.5.2

Git - client

[Security vulnerability CVE-2016-2324 & CVE-2016-2315] affects multiple Git versions. Both server and client Git installations should be updated to a patched maintenance version: 2.4.11, 2.5.5, 2.6.6 or 2.7.4 or newer. For instructions see Installing and upgrading Git.

Last modified on Mar 23, 2016

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.