This is the documentation for FishEye 3.2. View the latest version of

Unknown macro: {spacejump}

or visit the latest FishEye documentation home page.

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. However, if necessary you can set the exact path to the P4 client executable in FishEye, as described on this page, before you add Perforce repositories to FishEye.

Please see the  Supported Platforms page for information about the versions of Perforce that are supported by FishEye.

Configuration

To set the location of the Perforce client:

  1. Go to the admin area in FishEye.
  2. Click Server (under 'Global Settings').
  3. Click Edit Details (under 'Perforce client').
  4. Enter the path to your P4 (Perforce) binary executable.
  5. Click Update.
  6. Restart your FishEye server.

 

 

Files incorrectly considered binary

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. Please note that the repository will need to be reindexed in Fisheye after upgrading the P4 client for the changes to be picked up.

If you are unable to upgrade to a recent P4 client, the Repository Details page in FishEye 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.

 

 

 Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.