[FishEye Knowledge Base]
This page lists the supported platforms for FishEye 3.6.x and its minor releases.
Key: = Supported = Not Supported
Oracle JRE / JDK
FishEye 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 implementations have not been tested.
You can download an Oracle Java Runtime.
For the OpenJDK, download and install instructions for Linux flavours are at http://openjdk.java.net/install/.
Avoid using versions between 1.6.0_17 and 1.6.0_21 due to known performance issues.
Support for Oracle Java 7 is deprecated. See End of Support Announcements for Fisheye.
Support for Java 6 was removed in FishEye 3.6, as previously announced.
|OpenJDK||1.7 (Linux only)|
Apple Mac OS X
MySQL Enterprise Server 5.1+
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.
FishEye 3.3+ no longer supports PostgreSQL 8.2. See End of Support Announcements for FishEye.
For SQL Server:
FishEye 3.3+ no longer supports SQL Server 2005. See End of Support Announcements for FishEye.
9.0, 9.1, 9.2, 9.3
2008, 2008 R2
Bundled; for evaluation use only
Microsoft Internet Explorer
9.0, 10.0, 11.0
|FishEye 3.3+ no longer supports Internet Explorer 8. See End of Support Announcements for FishEye.|
Latest stable version supported
Latest stable version supported
Latest stable version supported
Version control systems
Native JavaHL 1.8
FishEye 3.1, and later, do not support the native JavaHL 1.6 client.
See Native support for SVN for discussion.
CVS (and CVSNT)
Client version 2007.3 or later
|Perforce Streams, introduced in 2011.1, is not currently supported. See - FE-3886Getting issue details... STATUS|
18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168
22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168
These are the versions of Git that we currently test FishEye against.
Externally-hosted repositories only are supported.
[Security vulnerability CVE-2014-9390] affects multiple Git versions. FishEye itself is not affected, however you should update your clients to a patched maintenance version: v22.214.171.124, v1.9.5, v2.0.5, v2.1.4 and v2.2.1 or newer.
3.0.2, 3.1.2, 3.2.3
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
1.5.1, 1.5.4, 1.6.4, 1.7.5, 1.8.4, 1.9.3
These are the versions of Mecurial that we currently test FishEye against.
As of version 3.6.3, FishEye supports Mercurial 3.
Mercurial 2.1 has a bug that makes it incompatible with FishEye. Please use Mercurial 2.1.1 or later.
You should restart FishEye after upgrading Mercurial.
Crowd server 2.4.x
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.|
FishEye to JIRA communication requires JIRA 5.0.x or later. Communication the other way, from JIRA to FishEye, depends on the JIRA FishEye Plugin.
Note that the JIRA FishEye Plugin is bundled with JIRA. If you are using a version of JIRA earlier than JIRA 5.0 you can upgrade the plugin in JIRA to get support for FishEye.
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).
|Monitor||Minimum screen resolution of 1024x768. Recommended screen resolution of 1280x768 or above.|
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 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.
Codebase size (HEAD of trunk)
FishEye index size
466 MB in 12151 files
115 MB in 11433 files
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.
FishEye can communicate with any repository running Subversion 1.1 or later.
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.
FishEye needs access to the
If you are using CVS, FishEye needs read-access to your CVS repository via the file system. It does not support protocols such as
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.
FishEye/Crucible is a standalone Java program. It cannot be deployed to web application servers such as WebSphere, Weblogic or Tomcat.
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.