Bitbucket Server 6.0 release notes
12 February 2019
Interested in trying this shiny new version of Bitbucket? Don't forget to renew your active software maintenance.
If you're upgrading from an earlier version, refer to the Bitbucket Server upgrade guide .
Also check our End of support announcements for Bitbucket Server and the changes in the API changelog .
The 6.0 changelog is at the bottom of this page.
In this new major version release we’ve updated Bitbucket Server’s foundations so we can continue to deliver you great features and improvements over the coming years.
In preparation for the future of the Java platform, we now support running on a Java 11 JRE. We’ve updated most of Bitbucket Server’s core, including Apache Tomcat, Spring Boot, Spring Framework, Hibernate, and other core dependencies. Additionally, we’ve updated our clustering middleware Hazelcast to bring greater reliability and performance to Data Center cluster installations.
Important notice to administrators
When upgrading to Bitbucket Server 6.0, Elasticsearch indexes that store search data will be recreated. This is due to a change requiring separate indexes for all document types, rather than a single index.
Recreating indexes will also result in a temporary degradation of Bitbucket’s search capabilities where code search results may be incomplete. Primarily, this impacts code search as these indexes may take hours to rebuild. It also impacts searching for projects and repositories by name, however these are typically indexed within a few minutes of Bitbucket Server being started after the upgrade.
You can see the reindex progress by going to:
1 <baseUrl>/rest/indexing/latest/status
Java 11 runtime support
Java 11 is the first long term support (LTS) version of Java since Java 8. Released in September 2018 it has vendor support for at least the next four years.
Bitbucket Server 6.0 introduces support for running on a Java 11 JRE, while continuing to support running on a Java 8 JRE (its installers still bundle and install a Java 8 JRE). As with previous releases, both Oracle's Java Runtime and standard builds of Open JDK are supported, so you can choose the one that best works for your organization.
For more information about supported Java Runtime environments check out our supported platforms.
A new way to add storage to Bitbucket Data Center
For Data Center customers with more data than they can fit on a single attached filesystem, we've added the ability to add more data storage locations. This will help customers with limits on the size of their attached storage. Check out adding additional storage for your repository data for more information.
New data store administration page
AJP connector support
When Bitbucket Server 5.0 switched from a standalone Tomcat distribution to using Spring Boot to start Tomcat, support for configuring AJP connectors was implicitly removed (only normal HTTP/1.1 connectors could be used).
In Bitbucket Server 6.0, support for configuring AJP connectors has been restored. This allows for reverse proxying Bitbucket Server with minimal configuration, and an efficient binary protocol for forwarding request and response data. Using AJP also means you don’t need to manually configure the correct "secure" settings for the connector, for example, when terminating SSL at a reverse proxy.
Supported platforms changes
We've added support for the following:
Java 11
Git 2.20
PostgreSQL 11
Elasticsearch 6.5
In this release, Bitbucket requires Git 2.11.0 or newer, excluding Git 2.12.2 on Windows.
We've also ended support for the following:
- All server installed versions of Git prior to 2.11 (client side Git version support is unchanged).
- Elasticsearch 2.3. See the Bitbucket Server 5.7 release notes for more details.
PostgreSQL 9.2.x and 9.3.x.
Please see supported platforms for a current list of supported platforms.
Backwards incompatible changes
As a major version release, Bitbucket Server 6.0 includes some backwards incompatible changes that may impact user-installed apps. These changes are typically made in order to remove legacy API/SPI where better alternatives exist, or to allow us to implement features and other improvements over the coming years.
To ensure that incompatible user-installed apps don’t interfere with the upgrade process, all user-installed apps are automatically disabled when you upgrade from a version older than 6.0 to 6.0 or newer. These apps can then be upgraded to 6.0 compatible versions (if they haven’t been already), then enabled and verified individually.
Below are two examples of API changes. For a more API changes in Bitbucket Server 6.0 please refer to the API Changelog.
1. Removal of the legacy Repository Hooks API
Bitbucket Server 5.0 introduced a new Repository Hooks and Merge Checks API. In 6.0 the legacy API has been removed. For an overview of the new API please see the Repository Hooks and Merge Checks Guide.
2. Removal of direct access to repositories on disk
In Bitbucket Server 5.10 direct access to the Bitbucket managed repositories on disk for plugins was deprecated. In 6.0 the deprecated API that permitted this has been removed. For more information please see the changelog entry for 5.10.
Upgrading?
We've included a handy upgrade matrix to help you quickly and easily see what features are included in each supported release.
Changelog
This section contains information about Bitbucket Server 6.0 minor releases. These releases will be free to all customers with active Bitbucket Server software maintenance.
If you're upgrading from an earlier version of Bitbucket Server, check the Bitbucket Server upgrade guide.
Listed below are highlights of all resolved issues for Bitbucket Server 6.0.x releases. They are ordered by votes received.