Stash is now known as Bitbucket Server.
See the

Unknown macro: {spacejump}

of this page, or visit the Bitbucket Server documentation home page.

This page lists the supported platforms for Stash 3.5.x.

See Integrating Stash with Atlassian applications for information about supported versions of JIRA.

See End of support announcements for Stash for upcoming changes to platforms supported by Stash.

 

Key: (tick) = Supported  (warning) = Deprecated  (error) = Not Supported

Hardware

CPU

1 core - Evaluation
2+ cores - Production 

  • If you are evaluating Stash, we recommend you use a server with at least 2GB of memory.
  • Aside from the memory allocated for Tomcat (768MB is the default configuration and suitable for most uses) additional memory and CPU capacity is required to support Git operations
  • The resources required for a full production deployment depend on the number and frequency of Git operations and the number of active users. See Scaling Stash for further discussion of hardware requirements for production environments and more details on how memory allocation is done by Stash and Git.
Memory2GB+

 

Operating systems

Apple Mac OS X(tick) Evaluation
(error) Production
  • Stash is a pure Java application and should run on any platform, provided all the Java requirements are satisfied.

  • In production environments Stash should be run from a dedicated user account.

  • Although Stash can be run in virtualised environments, Atlassian is not yet able to provide technical support for performance-related problems in a virtualised environment. If you do choose to run Stash in a virtual machine, please ensure that you choose a VM with good IO throughput and sufficient free memory. See hardware requirements for further details.
  • (error) Apple Mac OS X is not supported for production deployment.
  • (error) Microsoft Windows is not supported for 500+ Enterprise tiers.

 

Linux(tick)

Microsoft Windows

(tick) < 500 users
(error) 500+ Enterprise

 

Java

Oracle Java

(tick) 1.8
(warning) 1.7
(error) 1.6

  • We recommend using Oracle JRE 8, which you can download from the Oracle website.
  • For Java 8 we recommend 1.8.0u40+ to avoid critical defects in older versions.
  • Stash only requires the Java JRE, not the JDK.
  • For OpenJDK, download and install instructions for Linux flavors are athttp://openjdk.java.net/install/.
  • Note that the Stash installer will install a supported version of the Oracle Java JRE, which is only available to Stash, if necessary. See Running the Stash installer.
  • (error) OpenJDK >= 1.8u25 and < 1.8u40 are not supported due to a severe defect, Bug 1167153. This was fixed in 1.8u40.
  • (error) Support for Java 6 was removed in Stash 3.0, as previously announced.
  • (warning) Support for Java 7 is deprecated, and will be removed in Stash 4.0. See End of support announcements for Stash.

Pre-installed Java on some AWS EC2 Linux instances might be installed with a subset of features. See  SSH server fails to start on AWS EC2 instance for more information.

OpenJDK

(tick) 1.8u0 - 1.8u20

(tick) 1.8u40+

(error) 1.8u25+
(warning) 1.7 
(error) 1.6

Databases
HSQLDB

(tick) Evaluation
(error) Stash Data Center

Microsoft SQL Server / Microsoft SQL Server Express

(tick) 2014
(tick) 2012
(tick) 2008 R2
(tick) 2008

(tick) 2005

 
MySQL

Stash Server:

(tick) 5.6.16+
(tick) 5.5.x
(tick) 5.1.x

(error) 5.7+
(error) 5.6.0 – 5.6.15

 

(error) Stash Data Center

 

MySQL, while supported by Stash Server, is currently not recommended, especially for larger instances, due to inherent performance and deadlock issues that occur in this database engine under heavy load.

Affected systems may experience slow response times, deadlock errors and in extreme cases errors due to running out of database connections. These issues are intrinsic to MySQL (no other database engine supported by Stash shares this behavior) and are due to the way MySQL performs row-level locking in transactions. See http://dev.mysql.com/doc/refman/5.0/en/innodb-deadlocks.html for some general information on this.

Stash does its best to work around the MySQL behavior - see issues STASH-4517, STASH-4701 and others, for example. But under very heavy load you will generally get better performance with any of the other database engines supported by Stash (such as PostgreSQL, which is also freely available) than you will with MySQL.

 

  • (error) MySQL 5.6.15 and earlier: Note that Stash does not support versions of MySQL 5.6 earlier than 5.6.16 at all, because of bugs in its query optimizer (#68424, #69005). See Connecting Stash to MySQL for more information.
  • (error) MySQL 5.7+ is not supported.

  • (error)  MySQL (any version) is not supported in Stash Data Center.

Oracle

(tick) 12c
(tick) 11g

 

PostgreSQL

(tick) 9.0, 9.1, 9.2, 9.3
(tick) 8.2, 8.3, 8.4

 

Web browsers

Chrome(tick) Latest stable version supported

 

Firefox(tick) Latest stable version supported  

Internet Explorer

(tick) 11
(tick) 10
(tick) 9
(error) 8

Safari

(tick) Latest stable version supported

 
DVCS

Git – server

The table lists the versions of Git that have been tested against the  Stash 3.5.x releases.

  • In general, we recommend using the most recent version of Git on both the Stash server and clients, where possible, and subject to the following notes and exceptions.
  • The version of Git installed on machines that interact with Stash must be compatible with the version of Git installed for use by the Stash server.
  • For Git 1.9.0 and later we only test the highest bugfix release – all earlier bugfix releases in that series are also supported, unless specifically indicated otherwise below.
  • (warning) Support for versions of Git earlier than v1.8 on the server is deprecated and will be removed in Stash 4.0. See End of support announcements for Stash.
  • (warning) Git 1.8.3.x has some performance regressions which may cause problems in Stash with large repositories.
  • (error) Cygwin: Cygwin Git is not supported for use on Windows servers, regardless of version.
  • (error) Git 1.7.1 is not supported.
  • (error) Git 1.8.4.3 is not supported due to a critical bug in how symbolic refs are handled which breaks pushing and pulling for repositories with pull requests. (Details)
    STASH-4101 - Getting issue details... STATUS
  • (error) Git 2.0.2 and 2.0.3 are not supported due to a critical bug in git diff-tree which breaks Stash's commit page. (Details)
    STASH-5052 - Getting issue details... STATUS

[Security vulnerability CVE-2014-9390] affects multiple Git versions. Stash itself is not affected, however end-users should update their clients to a patched maintenance version: v1.8.5.6, v1.9.5, v2.0.5, v2.1.4 and v2.2.1 or newer. For instructions see  Installing and upgrading Git.

 

   
SupportedTested
LinuxWindows
2.2.02.2.0 
2.1.0+2.1.3 
2.0.0–2.0.1
2.0.4+
2.0.4  
1.9.0+1.9.41.9.4
1.8.0–1.8.4.2      
1.8.4.4+
1.8.0.3      
1.8.1.5  
1.8.2.3  
1.8.3.4  
1.8.4.5  
1.8.5.5
1.8.0      
1.8.1.2      
1.8.3      
1.8.4      
1.8.5.2
1.7.6+ (warning)  1.7.6.6      
1.7.7.7      
1.7.8.6      
1.7.9.7      
1.7.10.5  
1.7.11.7  
1.7.12.4
1.7.6      
1.7.7.1      
1.7.8      
1.7.9      
1.7.10      
1.7.11 
Git – client (tick) 1.6.6+

[Security vulnerability CVE-2014-9390] affects multiple Git versions. Stash itself is not affected, however end-users should update their clients to a patched maintenance version: v1.8.5.6, v1.9.5, v2.0.5, v2.1.4 and v2.2.1 or newer. For instructions see  Installing and upgrading Git.

Additional tools
Perl(tick) 5.8.8+ 
Mail clients
Apple Mail(tick) Apple Mail 4 
Gmail(tick) Latest 
iOS Devices(tick) iPhone, iPad 
Microsoft Outlook (tick) Express, 2007, 2010 
Outlook.com / Hotmail / Windows Live Mail
(tick) Latest 

Notes:

Deploying multiple Atlassian applications in a single Tomcat container is not supported. We do not test this configuration and upgrading any of the applications (even for point releases) is likely to break it.

Finally, we recommend not deploying any other applications to the same Tomcat container that runs Stash, especially if these other applications have large memory requirements or require additional libraries in Tomcat's lib subdirectory.

  • No labels