Supported platforms
This page lists the supported platforms for Fisheye 4.8 and its bug-fix 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
Java | ||
|---|---|---|
Oracle Java |
| 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. Please note:
|
OpenJDK |
| |
Operating systems | ||
Microsoft Windows |
|
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. |
Linux |
| |
Apple Mac OS X |
| |
Databases | ||
| 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. |
MySQL |
| |
PostgreSQL |
| PostgreSQL 12 is supported since Fisheye 4.8.5. PostgreSQL 13&14 are supported since Fisheye 4.8.9. |
Oracle |
| Oracle 19c is supported since Fisheye 4.8.5. |
SQL Server |
| SQL Server 2019 is supported since Fisheye 4.8.5. |
Web browsers | ||
Internet Explorer |
| |
| Microsoft Edge | Latest stable version supported | Legacy and Chromium. |
Mozilla Firefox |
| |
Safari |
| |
Chrome |
| |
Version control systems | ||
Subversion | Server:
Client:
| |
CVS (and CVSNT) |
| |
Perforce |
| The Server must support the ztag tagged protocol.
|
Git |
| These are the versions of Git that we currently test Fisheye against. Git for Windows is the only supported distribution when running Fisheye on Windows. Cygwin Git is not supported. |
Mercurial |
| These are the versions of Mercurial that we currently test Fisheye against. You should restart Fisheye after upgrading Mercurial. Use Mercurial compiled with Python 2.7, Fisheye is incompatible with Mercurial built with Python 3.
Mercurial on Windows does not provide support for non-ASCII characters in file names and paths. Read more about it in:
FE-7094
-
Getting issue details...
STATUS
|
| Atlassian applications | ||
| Crowd |
| |
| Jira | Jira 6.4+ | 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. |
Containerization
You can use official images to deploy FishEye in a Docker container, or customize a Docker deployment on your own.
We support the Atlassian Docker templates and can help with FishEye related problems. We do not provide support for Docker itself or problems with any Docker environment.
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.
Component | Specifications |
|---|---|
CPU | 1.8GHz or higher, a single core is sufficient. More cores or higher GHz will result in better load-handling ability. |
RAM | 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. |
I/O | 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 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 | Commits | Codebase size (HEAD of trunk) | Fisheye index size |
|---|---|---|---|
Subversion | 14386 | 466 MB in 12151 files | 647 MB |
CVS | 8210 | 115 MB in 11433 files | 220 MB |
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 |
CVS | 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.
WAR deployment
Fisheye/Crucible is a standalone Java program. It cannot be deployed to web application servers such as WebSphere, Weblogic or Tomcat.