Stash 3.4 release notes
21 October 2014
Introducing Stash 3.4
Today we're delighted to announce the release of Stash 3.4.
If you are upgrading from an earlier version of Stash, please read the Bitbucket Server upgrade guide.
Please also check the End of support announcements. Add-on developers will be interested in the API changelog.
The Stash 3.4 changelog is at the bottom of this page.
Batched email notifications
With Stash 3.4, we've taken a scalpel to our notifications engine and added email batching. What's more, we've made the notification emails more informative by putting the most important stuff at the top.
Now, notifications will be aggregated for each pull request and then emailed out for each recipient. The batch gets sent if things go quiet for a while (10 mins by default), or when the oldest notification gets 'stale' (30 mins by default), whichever comes first.
We think this is such a great improvement that we've made it the default, but you can change it back, in your personal account settings, if you prefer the rapid-fire pull request notifications.
Stash admins can control the batching behavior using system properties.
Read more about notifications in Stash...
Small improvements
JMX support
Stash 3.4 introduces new settings in setenv.bat and setenv.sh to simplify enabling JMX.
When JMX is enabled via setenv.bat or setenv.sh, administrators can now set jmx.enabled=true in stash-config.properties. When this is enabled, Stash will publish details about itself and its major libraries, including:
- BoneCP, publishing under
com.jolbox.bonecp, provides database connection pool statistics - Hazelcast, publishing under
com.hazelcast, provides clustering details for Stash Data Center - Hibernate, publishing under
org.hibernate.core, provides statistics for entities, queries and cache hits and misses
In addition, for those who wish to monitor Stash's "scm-command" and "scm-hosting" tickets, when jmx.enabled=true is set those counts are published under com.atlassian.stash on a Tickets entry. For both "scm-command" and "scm-hosting" JMX provides details on:
- How many tickets are configured
- How many tickets are available
- The number of requests currently queued for a ticket
- The timestamp at which the oldest waiter queued for a ticket
- The timestamp of the most recently rejected ticket
Support for Microsoft Office and OpenOffice/LibreOffice MIME types
We've extended the range of supported MIME types to include the Microsoft Office and OpenOffice document and template types (i.e. docx, dotx, pptx, potx, ppsx, xlsx, xltx, odc, otc, odb, odg, otg, odf, otf, odi, oti, odp, otp, ods, ots, odt, ott, odm, oth).
Aggregated group membership option for multiple user directories
We've added the option to 'blend' group memberships when a user or group is defined in two or more user directories. This is a change to how multiple directories were handled in previous versions of Stash. See the Bitbucket Server upgrade guide for information about the impact of this change.
Read more about using multiple directories...
Disabling pull request assistive URLs in the console
As of Stash 3.3, the console displays the URL to the 'Create pull request' screen in Stash after you push a new branch (or a branch with no pull requests yet). A Stash admin can disable this behavior as follows: click Manage add-ons in the Stash admin area, filter for 'bundled hooks' and click that, then disable the 'print-branch-links-hook' module.
Change log
This section will contain information about the Stash 3.4 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 the highlights of all those that have been resolved for the Stash 3.4.x releases.
21 December 2014 - Stash 3.4.5
Stash 3.4.4 was an internal release.
19 November 2014 - Stash 3.4.3
Stash 3.4.2 was an internal release.
7 November 2014 - Stash 3.4.1
21 October 2014 - Stash 3.4.0