Stash 2.7 リリース ノート
2013 年 8 月 20 日
Introducing Stash 2.7
Today we're pleased to announce Stash 2.7, which introduces a range of JIRA integration improvements, to help optimize your development workflows. We've also included a brand new Stash backup and restore solution.
If you are upgrading from an earlier version of Stash, please read the Stash upgrade guide.
Please also check the End of support announcements for Bitbucket Server.
The Stash 2.7 changelog is at the bottom of this page.
JIRA issue transitions
Now you can easily transition a JIRA issue from within Stash. For example, when creating a pull request you may want to transition the issue into review. Click on a linked JIRA issue anywhere in Stash to see a dialog with the available workflow steps:
Your Admin needs to have set up linking with JIRA before you'll see this. Read more about Jira integration in Stash.
Autolink JIRA issues in markdown
When you mention JIRA a issue key in Stash, for example in a pull request description or comment, the key gets automatically linked:
You can click on the linked key to see details for the issue. Note that issue keys in a URL will link directly to the JIRA instance, as you'd expect. Read more about Jira integration in Stash.
Support for multiple JIRA instances
Stash can now link to more than one JIRA server at a time, so different teams can work with their own projects in different JIRA instances, or a single team can link to issues across multiple JIRA servers.
Read more about Jira integration in Stash.
With the Stash 2.7 release we have made available a beta release of a backup and restore client for Stash. The Stash backup client locks access to Stash, checks that all Git and database operations have completed, and then performs a concurrent backup of the Stash database, repositories and data. You can download the Stash backup and restore client from the Atlassian Marketplace.
Although we are confident about the performance of this tool, we are interested in hearing how well it meets your requirements in actual use – this is why we are releasing the client as a beta. We look forward to your feedback!
Read more about backing up and restoring your Stash data.
Improved LDAP synchronization performance
We have greatly improved the performance for LDAP synchronization. For example, on a test LDAP server with 10,000 users and 10,000 groups, the time for a full synchronization improved from 64 minutes to 4 minutes.
The Repository System Information plugin is now deprecated
The functionality of the repository system information plugin has now been moved into core Stash. The plugin will still work for Stash 2.x versions but is redundant as of Stash 2.7.
Syntax highlighters are now configurable
You can now update the extensions associated with different syntax highlighters using the
stash-config.properties file in the Bitbucket Server home directory. For more details see Configuring syntax highlighting for file extensions.
MySQL default isolation level
Stash 2.7.x uses READ_COMMITTED instead of the MySQL default isolation level (REPEATABLE_READ). This can result in exceptions when installing/upgrading to 2.7.x, if binary logging is enabled in your MySQL server. More details and a fix can be found in this KB article.
This section will contain information about the Stash 2.7 minor releases as they become available. These releases will be free to all customers with active Stash software maintenance.
If you are upgrading from an earlier version of Stash, please read the Bitbucket Server upgrade guide.
The issues listed below are just the highlights of all those that have been resolved for the Stash 2.7 release.
11 November 2013 – Stash 2.7.6
5 November 2013 – Stash 2.7.5
15 October 2013 – Stash 2.7.4
15 October 2013 – Stash 2.7.3 (Internal release only)
19 September 2013 - Stash 2.7.2
29 August 2013 - Stash 2.7.1
20 August 2013 - Stash 2.7.0