Stash 3.8 release notes
1 April 2015
The Stash 3.8 changelog is at the bottom of this page.
Completely provision Stash automatically
Previously, even when installing Stash automatically, you still had to visit the Stash Setup Wizard in the browser to set the admin account, the Base URL and the external database connection, and to add the Stash license.
Now, by specifying all those settings in the Stash config properties file, you can completely install and set up a Stash instance automatically, without manual intervention. Stash will read the file, and apply those settings automatically after launching.
Read more about automated setup for Stash.
Monitor Stash performance with JMX counters
Stash now exposes instrumentation to provide better monitoring of Stash's performance. The range of metrics includes the number of projects and repositories, the number of Git pushes and pulls, and various thread pool metrics. These are all exposed as JMX counters, allowing you to use a JMX client, such as JConsole, to monitor Stash.
Deep linking into source file lines
We've improved how you can link to source files in Stash. Now you can Shift-click to select a range of lines, and Command-click (or Control-click) to add separate lines to the selection, then copy the updated URL for sharing with others.
Alternatively, you can modify the URL hash directly – for this selection it would be:
Note that Internet Explorer doesn't support Ctrl-clicking, unfortunately.
Cleaner handling of unlicensed and unauthorized users
We've tidied up how Stash handles unlicensed and unauthorized users pulled in from your external user directories.
Now, when you're picking reviewers for a pull request you'll only see those users who actually have permission to read the repository – unlicensed and unauthorized users aren't listed, so you don't have to waste time working that out for yourself.
We've also cleaned up @mentions in Stash – users without a Stash license are now never displayed in the @mentions picker anywhere in Stash. As always, notifications are only sent to those who have permission to read the repository.
server.xml file has been relocated
In Stash 3.8, the
server.xml configuration file has been moved to
<Stash home directory>
/shared/server.xml . If you have customized this file, you will have to copy it into this new location when upgrading to Stash 3.8. But once the configuration file is in your Stash home directory, you should not need to change it on future upgrades. See the upgrade notes for Stash 3.8.
Stash Data Center node IDs
You can now assign human readable node names to Stash Data Center that are consistent for the lifetime of a node, and stable across restarts. See Adding cluster nodes to Stash Data Center
Better support for
For developers hosting Go libraries in Stash, you can now use the
go get command without specifying a VCS suffix.
This section will contain information about the Stash 3.8 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, check the Bitbucket Server upgrade guide.
The issues listed below are the highlights of all those that have been resolved for the Stash 3.8.x releases, and are ordered by votes received.