Bitbucket Support

7 February 2023

Introducing Bitbucket Data Center and Server 8.8.

Highlights include:

Stricter controls on repository settings
Automate at scale with project-level webhooks
Authorization and permissions performance improvements

Stricter controls on repository settings DATA CENTER

We’ve added tighter controls on repository settings to help you meet your security and compliance needs and create consistent settings across all repositories in your project.

Project admins can now prevent changes to repository settings using the new controls available on project settings pages. You can be confident that important settings configured in bulk at the project level won’t be changed at the repository level.

Starting with Bitbucket 8.8, this feature is available for Project permissions, HTTP access tokens, and Access keys pages.

Learn how to restrict repository-level changes

Automate at scale with project-level webhooks SERVER DATA CENTER

Project admins can now create webhooks at the project level instead of creating webhooks for each repository. Repository admins can view these webhooks and avoid creating duplicate webhooks. Learn how to manage webhooks

Other improvements to webhooks

We’ve made some more changes to webhooks so you can integrate Bitbucket better with your dev tools.

Two new webhook events:

Repository event: Secret detected
Pull request event: Target branch updated

You can now:

use variables in webhook URL: {project.key}, {repo.slug}, {repo.ref.branchName}, {pr.fromRef.branchName}, {pr.toRef.branchName} and send data to multiple URLs using a single webhook
configure webhooks to use HTTP basic authentication
make use of the additional data (commit hashes, commit messages, and commit authors) available in the payload of repository push webhook events
skip SSL verification to integrate with internal URLs that use a self-signed certificate

Authorization and permissions performance improvements

We’ve made a number of significant improvements to authorization checks (that is, checking if a user has permissions), which are particularly impactful for instances with large numbers of permissions, users and groups. Some highlights include:

Improved performance for single user authorization checks when caches are cold.
Improved performance for de-duplicating redundant permissions.
Improved performance for user selectors.
Added additional metrics to the support zip such as permission grant count, cache sizes, and cache hit/miss rates. These metrics will help you quickly troubleshoot permissions performance problems.

We’ve also added two new properties that can be used to help tune Bitbucket instances with large numbers of permissions, users, and groups. These properties are used to better size some caches:

sizing-hint.cache.users
sizing-hint.cache.groups

Learn more about in-memory-cache sizes

Before you upgrade to 8.8

SERVER DATA CENTER

H2 database migration requirement

The H2 database driver has been upgraded to the currently latest version 2.2.220. The upgrade has boosted data security.

If you’re upgrading to Bitbucket 8.8 and later or Mesh 1.5 and later, you’ll need to migrate the data manually to the upgraded Bitbucket or Mesh instance if:

you’re using a mirror
you’re using Bitbucket Server with a H2 database
you’ve set up Bitbucket Mesh

Learn more about how to migrate your H2 database

Updates to supported platforms

Bitbucket 8.8 now includes support for running:

Git 2.39
Java 17

Get ready to upgrade

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

Renew now

As part of our new pull request experience from version 7.0 and higher, we have created a collection of new features for you to check out on one page, Enhancements to your code review workflow.