Bitbucket Server 4.11 release notes

8 November 2016

If you are upgrading from an earlier version, check the Bitbucket Server upgrade guide. Also, be sure to see the End of support announcements and the changes listed in the API changelog.

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

Try Bitbucket Server 4.11

See what's changed since your last review with iterative review

When a pull request is updated, Bitbucket Server will show you what has changed since you last reviewed it.

For reviewers, this means no more hunting through files for edits or re-reviewing code you've already seen. Upon returning to the updated review, Bitbucket Server will automatically display the number of commits since your last review and a corresponding diff. This allows you to comment on only those unreviewed commits. 

For authors, getting that second review after you've incorporated feedback is less painful. So you can merge your changes with confidence that each change was reviewed.

You can read all about conducting code reviews with pull requests on the page Reviewing a pull request.

Adaptive throttling of SCM hosting operations

Bitbucket Server 4.11 introduced a new throttling approach for SCM hosting operations that adapts to the stress the machine is under, referred to as adaptive throttling. With adaptive throttling, Bitbucket examines the total physical memory on the machine and determines a maximum ticket number that the machine can safely support given an estimate of how much memory a hosting operation consumes, how much memory BBS needs, and how much search needs. The default minimum (1 ticket per CPU core) and maximum (12 tickets per CPU core) of the ticket range can be changed.

Other characteristics of adaptive resource throttling:

  • Allows a variable range of ticket values depending on how close current CPU usage is to a target CPU usage (defaults to 75% CPU usage). This can be changed.
  • Every 5 seconds it resamples the CPU usage and recalculates how many tickets within the range can be supported.
  • CPU readings are smoothed so as to not respond too suddenly to CPU spikes and overshoot/undershoot the optimum number of tickets. 

Read about the new adaptive throttling properties on the Bitbucket Server config properties page, or read all about Scaling Bitbucket Data Center

Accessibility is important - Bitbucket Server VPAT compliance

Making our products and services accessible to all individuals is part of Atlassian's company values. We're auditing our products to ensure they are compliant with Section 508 and WCAG 2.0 AA.

Bitbucket Server has been reviewed in accordance to the Section 508 accessibility standards. You can read all about the evaluation on the page Bitbucket Server VPAT for Section 508 compliance

Changelog

This section will contain information about the Bitbucket Server 4.11 minor releases as they become available. These releases will be free to all customers with active Bitbucket Server software maintenance.

If you are upgrading from an earlier version of Bitbucket Server (or Stash), check the Bitbucket Server upgrade guide.

The issues listed below are the highlights of all those that have been resolved for the Bitbucket Server 4.11.x releases, and are ordered by votes received.

30 November 2016 - Bitbucket Server 4.11.2

T Key Summary
Loading...
Refresh

17 November 2016 - Bitbucket Server 4.11.1

T Key Summary
Loading...
Refresh

8 November 2016 - Bitbucket Server 4.11.0

T Key Summary
Loading...
Refresh

Last modified on Nov 30, 2016

Was this helpful?

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