This page last changed on Mar 16, 2008 by rkrishna.
On this page:
Error formatting macro: toc: java.lang.NullPointerException
Java Environment and Operating System
Java Runtime |
A JDK or JRE version 1.5 or greater. (Solaris requires 1.5.0_15 as a minimum)
You can download a Java Runtime for Windows/Linux/Solaris.
On MacOSX the JVM is available as part of the OS install here.
Once you have installed the JDK, you need to set the JAVA_HOME environment variable.
Note: There appeared to be a problem with some releases of the JRockit JVM that causes corrupted caches in FishEye. If you use JRockit, we recommend you use the latest JRockit 6 JVM. This problem has been confirmed on
- JRockit 5.0 JVM (R25.0.0-75)
- JRockit 5.0 JVM (R27.3.0)
|
Operating System |
FishEye is a pure Java application and should run on any platform provided the above requirements are satisfied. |
Platform 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).
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. |
Disk space |
Your budget for free disk space should meet or exceed a value three times the size of your repository data. For example, with 80GB of repository data, you should have 3 x 80GB, hence 240GB of free disk space dedicated to FishEye. |
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). |
Version Control System
At this time, FishEye supports the following source code management (SCM) systems:
Subversion (server) |
FishEye can communicate with any repository running Subversion 1.1 or later. |
Subversion (client) |
FishEye now bundles the SNVkit 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. |
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 pserver at the moment. |
Support for other version control systems (such as ClearCase) is planned for future releases. Let us know what SCM system you would like to see supported by logging and/or voting for a JIRA issue.
Deployment
FishEye/Crucible is currently a standalone Java program. It cannot be deployed to web application servers such as WebSphere, Weblogic or Tomcat.
|