Documentation for FishEye 3.0.x. Documentation for other versions is available too.

Skip to end of metadata
Go to start of metadata

This page shows the supported platforms for  FishEye 3.0.x and its minor releases.

Key: (tick) = Supported; (error) = Not Supported

Java Version




(tick) 1.6
(tick) 1.7

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

You can download a Java Runtime for Windows/Linux/Solaris. On Mac OS X, the JDK is bundled with the operating system. 

We highly recommend that you use the Oracle JVM (or use the default Mac OS X JVM), as other implementations have not been tested.

Please note:

  • Once you have installed the JDK, you must set the JAVA_HOME environment variable. See Installing FishEye on Windows or Installing FishEye on Linux and Mac.
  • 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.
  • If you intend to run FishEye as a Windows Service, using the Java Service Wrapper, we recommend that you use the Java JDK rather than the JRE so as to take advantage of the -server parameter.
  • You'll need the JDK for the JSP source download.

Note also that a bug in Java 1.6.0_29 and above will prevent a connection to an external SQL Server 2008 database without an additional workaround.

Avoid using versions between 1.6.0_17 and 1.6.0_21 due to known performance issues.

Operating Systems



Microsoft Windows


  • FishEye is a pure Java application and should run on any platform provided the requirements for the JRE or JDK are satisfied.
  • (warning) Although FishEye 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 chose to run FishEye in a VM, please ensure that you choose a VM with good IO throughput.



Apple Mac OS X






(tick) MySQL Enterprise Server 5.x
(tick) MySQL Community Server 5.x

The FishEye built-in database, running HSQLDB, is somewhat susceptible to data loss during system crashes.

External databases (such as MySQL) are generally more resistant to data loss during a system crash.

See the FishEye Database documentation for further details.

(warning) For MySQL 5.0, version must be 5.0.21 or later.

(warning) For MySQL 5.1, version must be 5.1.10 or later.

(warning) For MySQL 5.6, version must be 5.6.11 or later.


(tick) 8.2, 8.3, 8.4


(tick) 11g

SQL Server

(tick)2005, 2008, 2008 R2


(tick) Bundled; for evaluation use only

Web Browsers



Microsoft Internet Explorer

(tick) 8.0, 9.0
(error) 6.0 and 7.0 are not supported


Mozilla Firefox

(tick) Latest stable version supported
(tick) 3.6, 4.0



(tick) Latest stable version supported
(tick) 4, 5



(tick) Latest stable version supported

Version Control Systems




(tick) Server: 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.7
(tick) Client: SVNKit (default) or native client with JavaHL 1.6

Note that FishEye does not support SVN 1.7.x with the native client.

Version 1.8 support is currently being assessed. FishEye does not yet work for file:// access to repositories created with Subversion 1.8.



(tick) All versions



(tick) Client version 2007.3 or later



(tick) or later

Support for internal hosting of Git repositories by FishEye will end on August 14th 2013, after which Git internal hosting will be removed from newer versions of FishEye.

Please see End of Support Announcement for Internally Managed Repositories.


(tick) 1.5.1 or later

Mercurial 2.1 has a bug that makes it incompatible with FishEye. Please use Mercurial 2.1.1 or later. Mercurial 2.6.x is currently not compatible. You should restart FishEye after upgrading Mercurial.

Hardware requirements

FishEye 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 FishEye'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 with the FISHEYE_OPTS environment variable, adjustable up to 1024MB depending on performance.


FishEye's input/output is an important element of its overall performance. If FishEye 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).

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

Disk Space Requirement Estimates

Disk space requirements for FishEye 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 FishEye 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 FishEye instance uses over time, as needs for your specific environment may vary. It may be necessary to allocate more space than indicated here. Additionally, you can reduce disk space consumption by turning off diff storage in FishEye.

Deployment notes for version control systems

Subversion (server)

FishEye can communicate with any repository running Subversion 1.1 or later.

Subversion (client)

FishEye now bundles the SVNkit client, which becomes the default Subversion interface. An alternative is to use the native subversion client, using JavaHL bindings. Please see Subversion Client Setup for more information.

Perforce (client)

FishEye needs access to the p4 client executable. Due to some problems with earlier versions of the client, we recommend version 2007.3 or later.


If you are using CVS, FishEye needs read-access to your CVS repository via the file system. It does not support protocols such as pserver at the moment.

Support for other version control systems is planned for future releases. Let us know what SCM system you would like to see supported by creating a JIRA issue or adding your vote to an issue, if the request already exists.

WAR deployment

FishEye/Crucible is currently a Java program that runs on its own. 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 is bundled with the Crowd 2.4.1 client library, and supports the Crowd 2.4.x server.

Font size tips

(Especially for Linux users.) For best results you may want to tweak your default monospace font and font-size. The default browser font is usually Courier New which can be hard to read in some browsers. We recommend choosing the same font you use in your IDE and selecting a font size approximately 2 points larger than your variable width font. Firefox, Internet Explorer and Safari all have excellent font rendering. It is worth taking some time to tweak your fonts for the best experience.