Bitbucket Server 4.7 release notes

15 June 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 for Bitbucket Server and the changes listed in the API changelog.

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

Try it for free!

Add or delete tags to commits from within Bitbucket Server

Now, while viewing a commit within Bitbucket Server you can add and delete tags. Added tags can have descriptions as well. Only users with write access to the repo can add or delete tags, but users with read access can still view all tags associated with a commit.

Adding a tag to a commit

Deleting a tag from a commit

Rest and service API to manage pull request restrictions

As of Bitbucket Server 4.7.1, it is possible to manage pull request settings for a repository using REST. Refer to the Bitbucket Server REST documentation.

The new REST endpoint is located at:

/rest/api/1.0/projects/{projectKey}/repos/{repositorySlug}/settings/pull-requests

 

The endpoint accepts both GET and POST. Here's an example of what a GET response would look like:

{
  "requiredApprovers": 1,
  "requiredAllTasksComplete": false,
  "requiredSuccessfulBuilds": 0
}

 

 

An example POST request that updates the requiredApprovers and requiredAllTasksComplete for a pull request to be merged in a specified repository would be:

{
  "requiredApprovers": 2,
  "requiredAllTasksComplete": true,
}

 

The response would look like:

{
  "requiredApprovers": 2,
  "requiredAllTasksComplete": true,
  "requiredSuccessfulBuilds": 0
}

 

This is equivalent to the updated GET response. Note that not including the key for a particular setting in a POST request means that setting is won't be updated.

Additionally, it is possible for plugin developers to extend this REST endpoint, via the new Rest Fragment plugin module. An example of a plugin extending this REST endpoint can be seen in the Bitbucket Server Auto Unapprove plugin.

This functionality was added as a result of  BSERV-3644 - Getting issue details... STATUS .

Support for retrieving raw files from Bitbucket Server URLs

In previous versions of Bitbucket Server, sharing a URL for retrieving a raw file was difficult. To access a raw file within a repository, you would suffix a URL with ?raw, which could cause problems for some web server configurations.

With the release of Bitbucket Server 4.7.1, now there is a new, simpler syntax you can use to retrieve raw files. Here's an example of what the URL to browse to a file typically looks like:

http://yourserver.com/projects/{projectKey}/repos/{repositoryKey}/browse/file.extension

The URL needs to have the project key, repository key, and file path to access raw files, and this new functionality allows you to replace browse with raw to access the raw file (similar to selecting Raw file within the file view of the UI).

So, the URL to access the raw file would look like:

http://yourserver.com/projects/{projectKey}/repos/{repositoryKey}/raw/file.extension

This functionality was added as a result of  BSERV-4036 - Getting issue details... STATUS .

Change log

This section will contain information about the Bitbucket Server 4.7 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.7.x releases, and are ordered by votes received.

18 August 2016 - Bitbucket Server 4.7.2

T Key Summary
Loading...
Refresh

15 June 2016 - Bitbucket Server 4.7.1

T Key Summary
Loading...
Refresh

Bitbucket Server 4.7.0 was an internal release and is not available for download.

Last modified on Sep 27, 2016

Was this helpful?

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