Bitbucket Server 5.1 リリース ノート
2017 年 6 月 6 日
Bitbucket 5.1 の変更履歴は、このページの下部で参照できます。
GPG signed commits
With Bitbucket 5.1, we've added an additional security measure with the Verify Commit Signature hook, which rejects commits or tags not signed with a GPG key. GPG keys are a way to sign and verify work from trusted collaborators, and are a well-known industry standard. Coupling this with the Committer Verification Hook, you can rest assured that all the commits pushed to Bitbucket are valid and secure.
Want to know more?
- To learn about toggling hooks on and off in Bitbucket Server, see our repository hooks guide.
- For help with using GPG keys in your day-to-day work, have a look at the page Using GPG keys for guidance.
Next up is a highly requested improvement to our pull request workflow, the ability to delete open or declined pull requests. Have you ever created a pull request by mistake? Or found a pull request was obsolete? In Bitbucket Server 5.1, irrelevant pull requests can now be deleted (instead of merely declined), leaving your pull request history nice and clean. Pull request deletion is now enabled by default for pull request authors and repository administrators.
Last year we brought code search to Bitbucket Server, allowing teams to search for code across all repositories stored in Bitbucket. However for teams making extensive use of forks, the process of building an index for search could sometimes use a fair amount of disk space. In Bitbucket Server 5.1, we've introduced a way for administrators to keep search disk space under control with the ability to configure what gets indexed by Elasticsearch. For example, you can restrict the index process to exclude synced forks, which reduces disk space and provides refined search results. For our users with forked-based workflows, this should be a relief to limit disk space usage.
You can read about using this feature on the page Configure Bitbucket's code search index, or if you're already familiar with the
bitbucket.properties file you can see the options available on the Bitbucket Server config properties page - Search section.
Doc improvements around using Elasticsearch with Bitbucket Data Center
We've also improved our instructions for installing and configure a remote Elasticsearch instance for use with Bitbucket Data Center, providing more guidance on deploying an Elasticsearch instance. Check out these pages for more information:
- Improved Bitbucket Data Center installation instructions
- Instructions for Installing and configuring a remote Elasticsearch instance for Bitbucket Data Center
Have you checked out the new Atlassian Community yet?
We want to hear from you! It's not always easy to predict what customers will need to support them; there are so many ways Atlassian products can be configured a set up. The new Atlassian Community is a great way to discuss and ask questions about your configuration, and get general advice. If you'd like to see something we haven't provided yet in the doc, try posting a question on community.atlassian.com, and be sure to tag it with
elasticsearch so that we can learn how to support you better.
Power to the admins
The Bitbucket Server development team is always looking for ways to improve the lives of admins, and Bitbucket 5.1 is shipping the first of many improvements to make managing teams and data in Bitbucket Server easier.
- To give admins more control over their projects and repos, we've extend how you can configure Branching models, Branch permissions, and Default reviewers.
- Are your users taking advantage of Smart Mirrors? Well now they don't have to update their push URL when using a Smart Mirror over HTTPS. Huzzah!
Watch this space for more improvements to help admins do their jobs better.
このセクションには、Bitbucket Server 5.1 のマイナー リリースの公開後、それらの情報が追記されます。このリリースは、アクティブな Bitbucket Server ソフトウェア メンテナンスをお持ちのすべてのユーザーが無料で利用できます。
Bitbucket Server を以前のバージョンからアップグレードする場合は、Bitbucket Server アップグレードガイドを確認してください。
以下に Bitbucket Server 5.1.x リリースで解決済みのすべての課題の概要を、投票数の多い順に記載しています。