Perforce client setup
FishEye can communicate with any Perforce server, but it needs to use the p4 command-line client to do so.
By default, FishEye looks for the p4 executable in the current path. You can specify the exact path the the p4 executable you wish to use in the "Server Settings" in the FishEye Admin screens.
Some users have reported errors where FishEye considers some files to be binary when they are not. It appears this may be a limitation of earlier P4 clients. If you can upgrade to a recent P4 client (2006.1 onwards), this will fix this issue. You do not need to update the P4 Server. If you are unable to update, the admin UI allows you to set a limit on the size of filelog commands sent to the server. Setting this to something around 100 will fix the issue. It will, however, also impact performance significantly.