FishEye, Crucible 4.4 버전이 릴리스 되었습니다. 자세한 사항은 FishEye 4.4 릴리스노트 를 참조하십시요..
페이지 트리
메타 데이터의 끝으로 건너뛰기
메타 데이터의 시작으로 이동

21 February 2017

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.14 changelog is at the bottom of this page.

Try Bitbucket Server 4.14

Add access keys to branch permissions in Bitbucket Server 4.14

In Bitbucket Server you can give users read or write access to anything – a specific project, a single repository, or just a branch. You can also give permissions to access keys, which allow continuous integration servers and other automated processes to interact with your source code. Previously, access keys were granted only at the project and repository level, causing some trouble when branch permissions are also applied. The only way around this was to create a user for your CI server and explicitly grant it branch access like other members of your team. In Bitbucket Server 4.14, access keys are now applicable at the branch level, thus avoiding extra user creation. Updating repository metadata on restricted branches is as easy selecting an access key in the branch permission dialog.

Automatic updates and email reviewer status

Next up, 2 new features that make digesting information just a little bit faster. First an update to the personal dashboard - no more refreshing required. When changes are made to your pull requests, i.e. approval or comment, they'll be reflected automatically on the dashboard. Waiting for your pull requests to be reviewed? Then pop open a tab, sit back, relax, and watch the approvals roll in.


Second, an enhancement to pull request email notifications. Pull requests are imperative for ensuring high quality code, which is why we've built Bitbucket Server's pull request experience to cater to professional teams. Currently when updates to pull requests occur (i.e. a reviewer changes the status to 'needs work'), the subsequent email notification batches this change with many others. To get a good idea of all the activity, you'll need to open the email and scroll through the updates. In Bitbucket Server 4.14 you can now get a feel for changes by looking at the reviewer status in the notification header. A new 'needs work' status is a quick indicator that the pull request needs revisiting. 


Changelog

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


4 May 2017 - Bitbucket Server 4.14.5

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
새로 고침


29 March 2017 - Bitbucket Server 4.14.4

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
새로 고침


20 March 2017 - Bitbucket Server 4.14.3

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
새로 고침


13 March 2017 - Bitbucket Server 4.14.2

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
새로 고침


28 February 2017 - Bitbucket Server 4.14.1

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
새로 고침


21 February 2017 - Bitbucket Server 4.14.0

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
새로 고침


  • 레이블 없음