#bitbucketserver

In Bitbucket Server 6.6 we've added new features that lighten the load for admins and streamline the developer workflow.

What's new

Self-protect with rate limiting

Suggest changes directly in pull requests

Link projects between Bitbucket Server and other Atlassian Applications

For a list of resolved issues, check out the change log.

Get Bitbucket Server 6.6

Self-protect with rate limiting

Without protections in place, automated integrations and scripts can hammer your Bitbucket Data Center instance with huge bursts of requests, leading to drops in performance and downtime. This creates unnecessary work for admins who get paged (often after hours) to fix issues, and then have to comb through logs to find the culprit so it doesn’t happen again.Rate limiting changes all this by giving your Bitbucket Data Center instance the power to self-protect. Admins can now control how many HTTP requests (e.g. REST API requests) automations and scripts can make, and how often they can make them, meaning increased performance and team productivity (and hopefully for admins, more sleep too).Rate limiting is available for all Bitbucket Data Center customers.

See how to get started.

Suggest changes directly in pull requests

Commenting on a pull request isn’t an unfamiliar task. Having that comment quickly become the actual code change that you suggest is something new we think you’ll appreciate for this release of Bitbucket Server. Save time from the back-and-forth by providing feedback to make a suggested change directly in a pull request. Head over here to see how.

Link projects between Bitbucket Server and other Atlassian Applications

Project Links help to save time and prevent mistakes. For example, with Project Links set up between Bitbucket Server and Jira, when you create Bitbucket branch from Jira, repos from the linked Bitbucket project are prioritized in the repo list, making it easy to pick the right one. What's more, these links also work the other way, and when you create a Jira issue from a comment in Bitbucket the linked Jira project is pre-selected in the project list.Check out Configuring Project Links across Applicationsto learn more about connecting your projects, spaces, and repositories.

What else is new?

Git 2.23 now supported on the server. See our supported platforms page for more info.

Smart Mirrors with Bitbucket Cloud support

From version 6.6 onwards, Bitbucket Data Center must be used as the primary server for Smart Mirrors. To continue to use Bitbucket Cloud with Smart Mirrors, you’ll have to use version 6.5 or below. For details on setup and usage, see Smart mirroring for Bitbucket Cloud .

Interested in upgrading?

Before upgrading from an earlier version, check out our upgrade guide and

upgrade matrix. Remember to renew your active software maintenance too.

Renew now

Changelog

End of support announcements

API changelog

Issues in Release

Suggestion: Allow users to apply suggestions to pull requests

Fixed: Capital case username does not work with updating PR participant status API

Fixed: Project avatars do not include alternative text

Fixed: Initial attachments on pull requests cannot be seen by reviewers that have no access to source forked repository

Fixed: Escape pipe in code section of table leaves escape character

Suggestion: Support for Git 2.23

Fixed: StackOverflowError in org.commonmark.internal.InlineParserImpl

Fixed: Creating a branch via REST with an incorrect body returns a 500 response code

Fixed: Changing language in users Account setting on viewing individual commit of pull requests cause "error page not found" message

Fixed: Bitbucket sends email notifications to unlicensed users for pushed commits in a repository

Fixed: Announcement banner does not visually persist settings when saving the banner with a status set to "off"

Fixed: Clicking "Unable to access your account" for read-only directory users displays an erroneous message

Fixed: Help pop-up for system administrator global permissions have incorrect translation in French

Fixed: Filtering users by permission drops users depending on the page size

Fixed: Pushing a code with an unlicensed user is possible if it was once a licensed user and an SSH key is added to user's profile

With the release of Bitbucket Server 6.5, we are excited to bring you the latest information on new features, updates, and bug fixes.

A webhook dedicated to Smart Mirrors

A lock button for Git LFS files

For a list of resolved issues, check out the Changelog.

Get Bitbucket Server 6.5

What's new under the hood?

A webhook dedicated to Smart Mirrors

In preparation for the launch of mirror farms, we’re introducing a new webhook in this release that tells continuous integration systems when a mirror has finished synchronizing a set of changes.

With this webhook in place, CI systems are guaranteed to find the changes they would expect from a notification.

How it works:

A user pushes commits to a repository.

A synchronization prompt is sent to the mirror from the primary.

Once the mirror is synchronized, it reports back to the primary.

The primary then triggers the mirror sync webhook.

In the case where there is more than one standalone mirror in the repository, an additional webhook is triggered for each once they are synchronized.

A lock button for Git LFS files

Git LFS file locking is now even easier this release. With the click of a button, you can now lock or unlock files directly in Bitbucket Server’s source view.

What else is new?

A check for merging pull requests. This check blocks merging if any reviewers have marked the pull request as ‘needs work’.

An update to automatic branch merging. To stop automatic branch merging leading to merge conflicts that are challenging to resolve, you can now choose to block users from automatically merging pull requests if there are open downstream pull requests.

Bitbucket Server for Slack. Get updates about your Bitbucket Server repositories and perform key Bitbucket actions directly from your Slack channel. This integration is built and maintained by Atlassian with support back to Bitbucket Server 5.2. Take a look at theBitbucket Server for Slack documentation to see how to set it up.

Data Center infrastructure recommendations for Bitbucket

Is your instance close to outgrowing its size profile? It may be time to consider upgrading your infrastructure. Head over to Infrastructure recommendations for enterprise Bitbucket instances on AWS to check out our recommendations and results for large-sized instances, as well as full details of those test results.

Interested in upgrading?

Before upgrading from an earlier version, check out our upgrade guide and upgrade matrix. Remember to renew your active software maintenance too.

Renew now

Changelog

End of support announcements

API changelog

Issues in Release

Suggestion: Add Pull Request setting to block a merge if a Pull Request "Needs Work"

Fixed: Search results are not rendered correctly in IE11 and MS Edge when containing repositories on the results

Fixed: Creating projects in Bitbucket Server 5+ with upper and lower case letters results in non-alphabetical ordering

Fixed: Clone URL removes capitalization for context path

Fixed: Creating a pull request with nested groups enabled takes a very long time

Suggestion: The startup dialog mentions "https://confluence.atlassian.com/display/BitbucketServerKB/Troubleshooting+Installation" which has been changed and results in a "Page Not Found"

Suggestion: Log the branch name when branch gets deleted

Fixed: Opening "Clustering" page when Hazelcast IPv6 members configured with DNS names causes error 500

Development Task: Update Apache Tomcat dependency to 9.0.21

Fixed: Change DefaultPermissionVoterFactory's cache to avoid OutOfMemoryErrors

With the release of Bitbucket Server 6.4 comes a new feature for admins and a handy update for developers.

Our new built-in announcement banner

An update to Git LFS file locking

For a list of resolved issues, check out the Changelog.

Get Bitbucket Server 6.4

What's new under the hood?

Our new built-in announcement banner

Communicating scheduled downtime, upcoming maintenance periods, and other important info to your team is now much easier with our new built-in announcement banner. It appears at the top of Bitbucket Server where it can’t be missed. Forget about sending easily-ignored emails, and see how to make your first announcement here.

An update to Git LFS file locking

In Bitbucket Server 6.3 we introduced support for Git LFS file locking, which allows you to lock files to stop them from being edited while you work on them, helping you avoid merge conflicts. In this release we've made it even easier to see if a file is locked - in Bitbucket, a lock icon now appears next to locked files, and you can hover over it to see who locked the file and when.

Updates to supported platforms

Git support: Bitbucket Server 6.4 includes support for running Git 2.22 on the server.

Interested in upgrading?

Before upgrading from an earlier version, check out our upgrade guide and upgrade matrix. Remember to renew your active software maintenance too.

Renew now

Changelog

End of support announcements

API changelog

Issues in Release

Suggestion: Announcement Banner

Fixed: Japanese translation in quick search field is broken

Fixed: Deleting repository fork after moving repository and fork can delete original repository

Fixed: Bitbucket does not retrieve the default values for Jira fields

Suggestion: Merge check for duplicate open pull requests

Fixed: Git 2.21+: Ref sync produces verbose logging when requested ref cannot be found

Development Task: Support Git 2.22

Fixed: Upgrading AppLinks version to latest (5.4.15 & 6.0.6)

Fixed: Error on import repository feature running into "Error accessing remote repository"

Fixed: Changing public flag in Repository Permissions does not reflect on mirrors

With the release of Bitbucket Server 6.3 comes a couple of feature improvements that focus on the developer's experience.

Avoid conflicts with Git LFS file locking

Compare commits

For a list of resolved issues, check out the Changelog.

Get Bitbucket Server 6.3

What's new under the hood?

Avoid conflicts with Git LFS file locking

In an update to our Git Large File Storage (LFS) functionality, we’re introducing support for Git LFS file locking. On top of using Git LFS to speed up handling of large files, you can now also lock files to stop them from being edited while you work on them. This should help you avoid difficult-to-resolve merge conflicts when working with videos, 3D models, and other types of binary files.

We know many of you work in industries where locking these types of files is critical, and we hope this update unlocks a whole lot of productivity. For more information see Working with Git LFS filesand Enabling Git Large File Storage.

Compare commits

You can now quickly start comparing revisions by clicking Compare in the sidebar. What’s more, we’ve updated this feature so you can select a commit and compare it to another commit, branch, or tag. Sharing the results of your comparison with your team is also easy — you can simply send them the URL. See how to use Compare here.

Interested in upgrading?

Before upgrading from an earlier version, check out our upgrade guide and upgrade matrix. Remember to renew your active software maintenance too.

Renew now

Issues in Release

Suggestion: Add support for Git LFS File Locking API

Suggestion: Commit-level arbitrary diff (compare commits)

Suggestion: Allow ascii art for blocked commits to be removed

Fixed: Statistics about Webhook events can fail to update on Oracle databases

Suggestion: As an admin, I would like to be able to reindex the Jira indexes including the Jira keys included in the commit messages

Fixed: Fork Syncing warns about discard only for non-discard options

Fixed: Adding SSH base url parameters in bitbucket.properties doesn't set the base url

Fixed: Cannot use keyboard keys, such as page up & page down, to navigate on the code search screen.

Development Task: Update Apache Tomcat dependency to 9.0.19

Suggestion: Handle "implicit directory rename" conflicts (Git 2.18+)

Bitbucket Server 6.2 comes with a wide range of improvements designed to streamline your workflow and minimize errors.

Get Bitbucket Server 6.2

What's new under the hood?

Add repository descriptions: Tired of playing repo roulette? Short descriptions can now be added to repos to provide additional context and make them easier to identify. You can add these when creating a repo, or through the repo settings page.

See absolute timestamps: For increased precision, you can now choose to view all timestamps in absolute format (e.g.: 7 Apr 2019 2:00PM), instead of relative format (e.g.: 2 days ago). Head to your account settings to make the switch.

View SVG source code: To streamline reviewing and working with SVGs, you can now directly see and edit their source code in Bitbucket. This can be done in both diff and source view.

Delete confirmation check: To prevent a project or repository from being deleted by accident (don’t worry if you’ve done this, we may have done it ourselves too 😞), there is now an additional check — users first have to enter its name.

Customize your support link: You can now set up the ‘Contact Support' link in your instance footer to get your users back up and running faster. Direct them to a custom URL (e.g.: that of your support desk) or to send an email (e.g.: to a system admin). For more info, look for footer.links.contact.support on our config properties page.

Support for Git 2.21: Bitbucket Server 6.2 includes support for having Git 2.21 installed on the server.

Interested in upgrading?

Before upgrading from an earlier version, check out our upgrade guide and upgrade matrix. Remember to renew your active software maintenance too.

Renew now

Changelog

End of support announcements

API changelog

Issues in Release

Suggestion: Description for repositories

Development Task: Add support for Git 2.21

Fixed: Tag creation does not display vetos when canceled

Suggestion: As an administrator, I want to remove the "Contact Support" link from the Login screen and the footer in general

Fixed: Non-UTF8 characters in tags cause pull request to display HTTP 500 error

Fixed: Some of the letters in project and repository selectors are cut from the bottom

Fixed: Permission changes do not display vetos when canceled

Fixed: Moving a repository does not display vetos when canceled

Fixed: Repeatedly running integrity checks can repeatedly decline pull requests that are in an inconsistent state

Fixed: Repository Integrity Checks fail to create missing repositories

Fixed: Annotated tags created via the UI do not get correctly synced to forks

Fixed: Tag deletion UI doesn't handle vetoes

Fixed: Downloading LFS files from an HTTP mirror does not work

Fixed: Invalid json is returned when Git LFS requests return error messages

Fixed: Loading pull request metadata for branches can timeout unexpectedly

This release comes hot on the heels of version 6.0 and includes a new feature - a built-in commit graph.

Get Bitbucket Server 6.1

Our new built-in commit graph

To make it easy to find commits, understand the relationships between them, and visualize your entire repository, we’re introducing a new built-in commit graph. This sought-after feature now means you can quickly see your commit history and get to work faster.

The commit graph can be hidden when not needed

Bitbucket Server ships with its commit graph turned on by default. If you have a commit graph add-on you’d prefer to use, simply edit your bitbucket.properties file so:

feature.commit.graph=false

then restart your Bitbucket Server instance.

For more features and how to set them up, see Bitbucket Server config properties.

Interested in upgrading?

Before upgrading from an earlier version, check out our upgrade guide and upgrade matrix. Remember to renew your active software maintenance too.

Renew now

Changelog

End of support announcements

API changelog.

Issues in Release

Suggestion: Add commit graph

Fixed: Attempting to create several instances of the same pull request at the same time can give a 500 error code

Fixed: Error "Could not read loose ref" occurs when viewing files on a branch called "config"

Fixed: Jira referencing to removed commit after amending a commit

Development Task: Upgrade applinks to 6.0.4

Fixed: Contributing guidelines link doesn't show on pull request create form if coming from compare page

Fixed: Enabling SSL on additional connectors can cause NullPointerExceptions

Fixed: When using Windows, adding a Branch Permission to a Branch by name at the Project level with "*" in the name causes 500 errors

Fixed: Users with access to repo can see admin settings for that repo

Fixed: The frontend should not send the request to accept a mirror twice

Fixed: "Invalid cookie header" warnings are thrown on the console while running the installation wizard on Linux

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.

Try Bitbucket Server 6.0

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 disk, 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.

6.0 Supported platforms changes

In Bitbucket Server 6.0, we've added support for the following platforms:

Java 11

Elasticsearch 6.5

We've also ended support for the following platforms:

All versions of Git prior to 2.11:

In this release, Bitbucket requires Git 2.11.0 or newer, excluding Git 2.12.2 on Windows.

Elasticsearch 2.3. Full details on the Bitbucket Server 5.7 release notes.

PostgreSQL 9.2.x and 9.3.x.

Please see Supported platforms for a current list of supported platforms.

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.

<No Data>

Interested in trying a shiny new version? Don't forget to renew your active software maintenance! Renew now.

If you are upgrading from an earlier version, refer to the Bitbucket Server upgrade guide.

Be sure to also check the End of support announcements for Bitbucket Server and the changes listed in the API changelog.

The Bitbucket 5.16 changelog is at the bottom of this page.

Try Bitbucket Server 5.16

Anonymization in Bitbucket Server and Data Center

In the 5.16 release, we've refined our existing delete functionality by adding the ability to anonymize deleted user accounts.

When you anonymize a user in Bitbucket Server and Data Center:

The username is replaced with a non-attributable alias.

User mentions are replaced with a non-attributable alias.

If the user had a personal project, the personal project name and key is updated to a non-attributable alias.

User cleanup for deletion happens immediately, if it hasn’t already taken place (eg. deleting avatars, SSH keys, permissions).

The following data will remain after a username is anonymized:

User content (such as comments and pull requests).

User data in Git history.

The detailed procedure for deletion and anonymization can be found here. You can also refer to the Bitbucket Server and Data Center full GDPR Support Guides.

Deploy Bitbucket Data Center on Azure

More and more organizations are moving away from maintaining physical servers and embracing private cloud solutions, such as Microsoft Azure, for hosting their business critical applications.

We now provide a reference implementation template to help you deploy Bitbucket Data Center in Azure. The template can be modified to suit your needs, and you can deploy via the Azure Marketplace or using the CLI, it's up to you.

It's particularly good for trialing Bitbucket, without the need to provision your own hardware first.

Head to Getting started with Bitbucket Data Center on Azure to find out how it works.

Issues in Release

Fixed: In-line comments on pull requests are broken on IE11

Fixed: After upgrading to Bitbucket 5.13+, the following warning is reported in the logs

Fixed: The version of jQuery in use is vulnerable to several issues

Fixed: Go to dashboard keyboard shortcut stopped working

Fixed: ServletInputStream use after stream has been recycled

Fixed: Cannot retrieve code insight annotations if the target branch has copied a file since the source branch was created