Supported platforms

Still need help?

The Atlassian Community is here for you.

Ask the community

This page lists the supported platforms for  Crucible 4.4.x  and its minor releases.

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




Oracle JRE / JDK

(tick) 1.8

Crucible requires the Java Runtime (JDK or JRE), version as noted. Pre-release/Early access versions of Java are not supported.

We highly recommend that you use the Oracle JVM (or OpenJDK for Linux only). Other Java implementations have not been tested.

You can download an Oracle Java Runtime.

For the OpenJDK, download and install instructions for Linux flavors are at

Please note:

  • Once you have installed the Java, you need to set the JAVA_HOME environment variable. See Installing Crucible on Windows or Installing Crucible on Linux and Mac for details.
  • If you are using a 64-bit JVM, please ensure that you've set your max heap size (--Xmx) to a reasonable value, considering the RAM requirements of your system.

(error) Support for Java 7 was removed in Crucible 3.9, as previously announced.

OpenJDK(tick) 1.8 (Linux only)
Operating Systems



Microsoft Windows


  • Crucible is a pure Java application and should run on any platform provided the requirements for the JRE or JDK are satisfied.

Although Crucible can be run in virtualized environments, Atlassian is not yet able to provide technical support for performance-related problems in a virtualized environment. If you do chose to run Crucible in a VM, please ensure that you choose a VM with good IO throughput.



Apple Mac OS X






(tick) Bundled; for evaluation use only

The Crucible built-in database, running HSQLDB, is somewhat susceptible to data loss during system crashes. We recommend that you do not use HSQLDB for production systems.

External databases are generally more resistant to data loss during a system crash and are more suited for production use.

See the  Crucible Database documentation  for further details.


(tick) MySQL Enterprise Server 5.5+
(tick) MySQL Community Server 5.5+

(error) Maria, Percona

For MySQL:

  • (error) For 5.6, versions earlier than 5.6.11 are not supported
  • (error) For 5.7, versions earlier than 5.7.5 are not supported
  • (error) Support for MySQL 5.1 was removed in Crucible 4.2. See End of Support Announcements for Crucible.
  • (error) MariaDB and Percona variants of MySQL are not supported, and are known to cause issues when used with Crucible.

(error) Support for PostgreSQL 8.3, 8.4, 9.0 and 9.1 was removed in Crucible 4.2. See End of Support Announcements for Crucible.

(error) Support for SQL Server 2008, 2008 R2 was removed in Crucible 4.2. See  End of Support Announcements for Crucible.


(tick) 9.2, 9.3, 9.4


(tick) 12c

(tick) 11g

SQL Server

(tick) 2014

(tick) 2012

Web browsers



Microsoft Internet Explorer

(tick) 11.0

Minimum screen resolution of 1024x768. Recommended screen resolution of 1280x768 or above.

(error) Support for Internet Explorer 10 was removed in Crucible 4.3. See End of Support Announcements for Crucible.

Mozilla Firefox

(tick)  Latest stable version supported



(tick) Latest stable version supported



(tick) Latest stable version supported

Version Control Systems



Subversion (SVN)

(tick) 1.5, 1.6, 1.7, 1.8, 1.9

(tick) SVNKit (bundled & the default)
(tick) Native JavaHL 1.9  
(tick) Native JavaHL 1.8
(tick) Native JavaHL 1.7

(error) Crucible 3.1, and later, do not support the native JavaHL 1.6 client.

See Native support for SVN for discussion.

(and CVSNT)

(tick) All versions



(tick) Client version 2007.3 or later
(tick) Server version 2005.1 or later

The Server must support the ztag tagged protocol.

(error) Perforce Streams, introduced in 2011.1, is not currently supported. See FE-3886 - Getting issue details... STATUS


(tick) 2.12.2

(tick) 2.11.1

(tick) 2.10.2

(tick) 2.9.0, 2.9.3

(tick) 2.8.4

(tick) 2.7.4

(tick) 2.6.6

(tick) 2.5.5

(tick) 2.4.11

(tick) 2.3.10

(tick) 2.2.3

(tick) 2.1.4

(tick) 2.0.5

(tick) 1.9.5



These are the versions of Git that we currently test Crucible against.

(error) Git is not supported. See STASH-4101 - Getting issue details... STATUS

[Security vulnerability CVE-2014-9390] affects multiple Git versions. Crucible itself is not affected, however you should update your 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.

Git for Windows is the  only supported distribution  when running Crucible on Windows. Cygwin Git is  not supported  and has known issues.





(tick) 4.2 (since Crucible 4.4.1)

(tick) 4.1.3

(tick) 4.0.2

(tick) 3.0.2, 3.1.2, 3.2.4, 3.3.3, 3.4.2, 3.5.2, 3.6.3, 3.7.3, 3.8.4, 3.9.2

(tick) 2.0.2, 2.1.2, 2.2.3, 2.3.2, 2.4, 2.5.2, 2.6.3, 2.7.2, 2.8.2, 2.9.1

(tick) 1.9.3

These are the versions of Mercurial that we currently test Crucible against.

As of version 3.6.3, Crucible supports Mercurial 3.

(error) Mercurial 2.1 has a bug that makes it incompatible with Crucible. Please use Mercurial 2.1.1 or later.

You should restart Crucible after upgrading Mercurial.

Atlassian applications  

(tick) Crowd 2.4.x+

(tick) Crowd client library: 2.4.1

From version 2.8.x, Fisheye bundles the Crowd 2.4.1 client library, and supports the Crowd 2.4.x server, and later versions.

(tick) Jira Fisheye Plugin 6.1.0+

(tick) Jira 6.4+

The Jira Fisheye Plugin is bundled with Jira. If you are using earlier versions of Jira you can upgrade the plugin in Jira to get support for Crucible.

Hardware requirements

Crucbile should ideally run on a dedicated server. The most important aspect for a large-repository deployment will be I/O speed. You definitely want a fast local HDD for Crucible's cache. Note that NFS and SAN are not supported.




1.8GHz or higher, a single core is sufficient. More cores or higher GHz will result in better load-handling ability.


1GB minimum, 2GB will provide performance "headroom". Your Java heap should be sized at 512MB.


Crucible's input/output is an important element of its overall performance. If Crucible accesses your repository remotely, make sure that the throughput is maximum and the latency minimum (ideally the servers are located in the same LAN, running at 100Mbps or faster).

MonitorMinimum screen resolution of 1024x768. Recommended screen resolution of 1280x768 or above.

While some of our customers run Crucible on SPARC-based hardware, Atlassian only officially supports Crucible running on x86 hardware and 64-bit derivatives of x86 hardware.

Disk space requirement estimates

Disk space requirements for Crucible may vary due to a number of variables such as the repository implementation, file sizes, content types, the size of diffs and comments being stored. The following table contains some real-world examples of Crucible disk space consumption.

Repository technology


Codebase size (HEAD of trunk)

Fisheye index size



466 MB in 12151 files

647 MB



115 MB in 11433 files

220 MB

(warning) These disk space estimates are to be used as a guideline only. We recommend you monitor the disk space that your Crucible instance uses over time, as needs for your specific environment may vary. It may be necessary to allocate more space than indicated here.

Deployment Notes for Source Code Repositories

Crucible can also store uploaded files in its own database, removing the need for any kind of repository. A number of external databases are supported when Crucible is used with Fisheye. See the Fisheye Supported Platforms.

WAR deployment

Fisheye/Crucible is a standalone Java program. It cannot be deployed to web application servers such as WebSphere, Weblogic or Tomcat.

Single sign on with Atlassian Crowd

From version 2.8.x, Fisheye bundles the Crowd 2.4.1 client library, and supports the Crowd 2.4.x server, and later versions.
Last modified on Oct 6, 2021

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.