This page lists the supported platforms for Fisheye 4.7.x and its minor releases. We cannot ensure the stability of Fisheye used with a platform or a versions that is not mentioned in this page.
Key: = Supported = Deprecated = Not Supported
Fisheye requires the Java Runtime (JDK or JRE), version as noted. Pre-release/early access versions of Java are not supported. We recommend that you use the Oracle JDK or Adopt OpenJDK as these are implementations we test Fisheye against.
Although Fisheye 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 choose to run Fisheye in a VM, please ensure that you choose a VM with good IO throughput.
Apple Mac OS X
|HSQLDB||Bundled; for evaluation use only|
The Fisheye 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 (such as MySQL) are generally more resistant to data loss during a system crash.
See the Fisheye Database documentation for further details.
5.6, 5.7 Enterprise Server
12c R1, R2
SQL Server 2016 and 2017 are supported since Fisheye 4.7.1.
Version control systems
Native JavaHL 1.8, 1.9, 1.10
Native JavaHL 1.7
CVS (and CVSNT)
2007.3 〜 2017.2
The Server must support the ztag tagged protocol.
Perforce Streams are not supported (FE-3886).
1.9.5, 2.0.5, 2.1.4, 2.2.3, 2.3.10, 2.4.12, 2.5.6
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: v188.8.131.52, 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 Fisheye on Windows. Cygwin Git is not supported.
4.2 (since Fisheye 4.4.1), 4.2.3
3.7.3, 3.8.4, 3.9.2
2.8.2, 2.9.1, 3.0.2, 3.1.2, 3.2.4, 3.3.3, 3.4.2, 3.5.2, 3.6.3
Crowd client library: 2.4.1
Fisheye to Jira communication requires Jira 6.4.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 6.4 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).
|監視||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 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.
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.
Deployment notes for version control systems
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.