This documentation relates to an earlier version of FishEye.
View this page in the current documentation or visit the current documentation home.

Skip to end of metadata
Go to start of metadata

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

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

Java Version


Oracle or Apple JRE / JDK (1)

(tick) 1.5 or 1.6

Operating Systems


Microsoft Windows (2)


Linux (2)


Apple Mac OS X (2)





(tick) MySQL Enterprise Server 5.0.21 or later
(tick) MySQL Community Server 5.0.21 or later


(tick) 8.0 or later


(tick) 11g


(tick) (bundled; for evaluation use only)

Web Browsers


Microsoft Internet Explorer

(tick) 7.0 or later, (error) IE6 is not supported

Mozilla Firefox

(tick) 3 or later


(tick) 4 or later

Version Control Systems


Subversion (SVN)

(tick) Server 1.1 or later
(tick) Client uses included SVNkit. Native JavaHL 1.6 or later may be used.


(tick) All versions

Perforce (P4)

(tick) Client version 2007.3 or later.
(tick) Server version 2005.1 or later. The Server must support the ztag tagged protocol


(tick) 1.6 or later

Mercurial (Hg)

(tick) 1.5.1 or later (Python 2.4.3 or later)

IBM ClearCase

(tick) 2003.06.10 or later

NOTE: The support for ClearCase will end on April 4th 2012, after which ClearCase functionality will be removed from newer versions of Crucible.

For more information please see End of Support Announcement for IBM ClearCase.

Supported Platform Notes

1. FishEye requires Java Runtime (JDK or JRE) version 1.5 or later (Solaris requires 1.5.0_15 as a minimum). 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. Note: It is highly recommended that you use the Oracle JVM (or use the default Mac OS X JVM), as other implementations have not been tested.
(info) Once you have installed the JDK, you need to set the JAVA_HOME environment variable.
(warning)  If 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.

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

3. The FishEye built-in database, running HSQLDB is somewhat susceptible to data loss during system crashes. External databases are generally more resistant to data loss during a system crash.

At this time, FishEye supports the following external databases:

Hardware Requirements

FishEye should ideally run on a standalone 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 (not NFS or SAN).




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 standalone Java program. It cannot be deployed to web application servers such as WebSphere, Weblogic or Tomcat.

Single Sign On with Atlassian Crowd

FishEye is bundled with the Crowd client library, and operates with Crowd 1.3 or later.

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 3, Internet Explorer 7 and Safari all have excellent font rendering. It is worth taking some time to tweak your fonts for the best experience.