Bitbucket Server 7.0 release notes
2020 年 3 月 05 日
We're excited to present Bitbucket Server and Data Center 7.0!
主なハイライト
Pull requests get a makeover
SERVER DATA CENTER
The pull request page has been redesigned and packed full of improvements to make your code review experience smoother, more enjoyable, and less of a tedious task.
Faster navigation in pull requests
With twice-as-fast content loading while switching between diffs, improved file navigation performance, and smooth scrolling in a side-by-side diff, you just might find yourself having fun speeding through your code reviews.
A more intuitive design
We've improved the pull request workflow, giving you a more effective and efficient experience.
Better collaboration in the diff view
- Commenting
- Comment anywhere in the diff, including on expanded lines of code that weren't changed as a part of the pull request.
- Comment on files stored via Git LFS.
- Syntax highlighting: Until now, syntax highlighting was only available on the side-by-side diff, but now it’s available in the unified diff too.
- Word wrap: No more horizontal scrolling to read lines of code in the diff.
- Expanding: Click Show more to expand all lines in the diff now, rather than just 10 at a time.
- Searching: You can now use your browser’s native Ctrl+F action to search for code in the file you’re viewing.
- Image thumbnails: Drag or attach an image into a comment and you’ll see a thumbnail-sized preview of it rather than having the full-sized image rendered.
Do more with less clicking
- Copying: You can now copy code from just one side of the side-by-side diff view without also copying code from the other one. Also, select and copy branch names in one click.
- Pasting: When you paste code from a pull request into a comment, we’ll automatically format it as a
code blockwith the correct syntax highlighting. - Editor: When you type into a comment or description editor in a PR, you'll see Markdown hints as you type, no need to preview until you’re ready to see the final view.
File-tree improvements
- Filtering: Easily locate changed files in a pull request using the new Filter file tree button. Use wildcards to find what you need faster on pull requests that have a great deal of files to look through. You can find it just above the file-tree, along with the Search code button. To see an example, check out Reviewing a pull request.
- Redesigned icons: Icons in the file tree view now have a more distinctive design with contrasting colors so that you can better recognize the relationship between them, and whether your file has been edited, added, removed, or modified.
Task improvements in a pull request
Create tasks in your pull requests without having to write a comment first. In fact, you can even convert comments into tasks. They also now support Markdown and rich content, like code snippets. Check the Reviewing a pull request page for more details.
We've got your code covered
SERVER DATA CENTER
Code Insights for Bitbucket Server offers a better way for your team to improve code quality by allowing continuous integration (CI) and other analysis tools to surface insights about code quality in pull requests. This is so issues that are related to code quality can be viewed and acted upon during a normal code review process. Now, you can access your code coverage results as a part of Code Insights.
Code coverage finds aspects of the code which may not have been covered adequately by tests. The results are compiled and displayed in the diff view using color-coded blocks which represent lines of code that are covered fully, partially, or not at all by tests. You can then also dig into a coverage report, if it’s provided, to see the actual lines that may not be covered and use that to identify critical parts of your application that still need to be tested.
More auditing capabilities for admins
SERVER DATA CENTER
We’ve made some improvements to auditing for projects and repositories, and expanded it to the global admin settings that displays all events in the system. Having this digital record gives admins the higher level of visibility that they need to ensure security and compliance.
Let’s talk about what you can do with auditing without having to leave Bitbucket:
→ You get one source of truth. Your audit log is now instance-wide and not limited to a project or a repository, so you can view all the events in one place.
→ You are now in control. You can decide which events are logged and how long you want to keep them. They are also ready to be exported if needed.
→ You get full transparency. You can search the logs using full-text-search capabilities, filter the events, and expand each event for further details.
Stay tuned, because we are in the process of continually adding value, with more to come. Right now, check it out yourself by going to the administration area and then click Audit log (under accounts). For more information about the feature, see View and configure the audit log.
Single sign-on with OpenID Connect
DATA CENTER
Many enterprises still struggle to use industry-standard user management tools to authenticate their users in Atlassian tools. A couple of months back, we added SAML support to all of our Data Center products, and now we're adding a new authentication option with the introduction of an OpenID Connect integration. This will enable seamless integrations with many 3rd party Identity Providers.
The plugin is available in Atlassian Marketplace for the the following Data Center products:
- Jira
- Bitbucket
- Confluence
For more information, see OpenID Connect for Atlassian Data Center applications.
A new webhook for source branch updates in a pull request
We have added a new webhook, Source branch updated. When the source branch of a pull request is updated, for example; new changes are pushed to the source branch after incorporating code review feedback, and the webhook is triggered.
Learn more about webhooks for Bitbucket Server
Enforcement of supported operating systems
Bitbucket Server can no longer run on unsupported operating systems. This is due to some improvements to memory consumption that required switching from using Java’s ProcessBuilder to manage git processes, to a different approach based on native operating system APIs.
This isn’t changing what platforms are supported, rather it’s simply enforcing the supported platforms we’ve always had.
In the Bitbucket Server 6.9 release, we put a check in place that detects whether or not you’re on a supported platform. If the system detects that you aren’t, we’ll display a warning banner and an alert in the UI. Now, for 7.0, if you’re on an unsupported operating system, you will see a system failure warning.
More details to help you determine what is supported can be found in our Supported platforms page.
A modified behavior for diffs
We’ve made the switch from a 3-way diff to a 2-way diff in pull requests. This means that from Bitbucket Server 7.0 and later, when viewing a pull request, the diff shown is one between the tip of the source branch and its common ancestor with the target branch. The UI will still indicate when a pull request has conflicts, but they will no longer be marked up in the diff. Use of a 2-way diff is an industry-standard and reduces CPU load on large instances.
refs/pull-requests/*/merge has been completely removed in 7.0 and will no longer be created or updated by the system again. With the switch from 3-way diffs to 2-way diffs, the system no longer retains the merges it creates to check merge-ability. Instead, it runs git merge to see what happens, and discards everything that results. This prevents the accumulation of “unreachable” pull request merge objects in repositories, which can (greatly) slow down (clone, fetch, pull, push) performance as they build up. Any tool that wishes to build a pull request’s merge will need to create that merge on its own, going forward.
Before upgrading, verify the refs used in your CI/CD pipeline to see if these changes will impact builds.
API changes
The Bitbucket Server client web fragment APIs are being replaced with the Atlassian client plugin on the pull request page. If you build your own integration or plugin, go to the API Changelog to see how this may impact you.
サポート終了のお知らせ
The following are no longer supported, starting in 7.0:
- Internet Explorer 11 as previously announced
- Legacy Microsoft Edge (versions 18 and earlier). Latest stable Chromium-based Microsoft Edge continues to be supported.
- MariaDB 10.0
- Hipchat integration for Bitbucket Server
サポート対象プラットフォームの更新
Bitbucket Server 7.0 now includes support for running:
- Git 2.25 for Server
- Microsoft SQL Server 2019
Deprecations
- MariaDB 5.5
- MySQL 5.5
- Elasticsearch 5.5.x
アップグレードの準備
以前のバージョンからのアップグレードをご検討の場合、アップグレード ガイドとアップグレード マトリクスをご参照ください。また、アクティブなソフトウェア メンテナンス ライセンスが更新済みであることをご確認ください。
Upgrading from an older version? Check out the Bitbucket Server 6.10 Enterprise Release Change Log for a collection of all the changes between Bitbucket Server 6.0 and 6.10.
See our bug fix and security bug fix policies for more information.
変更履歴
Bitbucket Server 7.0.5 で解決済みの課題
2020 年 6 月 10 日にリリース
Bitbucket Server 7.0.4 で解決済みの課題
2020 年 5 月 5 日にリリース
Bitbucket Server 7.0.3 で解決済みの課題
Released 07 April 2020
Bitbucket Server 7.0.2 で解決済みの課題
Released 01 April 2020
Bitbucket Server 7.0.1 で解決済みの課題
Released 09 March 2020
Resolved issues in Bitbucket Server 7.0
Released 05 March 2020