All Versions
Fisheye 4.2 DocumentationFisheye 4.1 Documentation
Fisheye 4.0 Documentation
More...
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. To specify the exact path of the p4 executable, click 'Server Settings' in the FishEye 'Admin Menu'.
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.
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.
10 Comments
Anonymous
Apr 26, 2011Hello, is there documentation on dealing with the error below?
I have tried setting the P4PASSWD environment variable when starting fisheye but still run into the same issue.
Thanks for any assistance
Gregory Kellum
Jun 08, 2011I have been having the same problem. I've tried multiple users, but I keep getting this invalid password error.
cdli99
Oct 29, 2011Looks like FISHEYE only like depot ending with "/", for example, in my case:
Anonymous
Oct 07, 2011Hello
I have been having the same problem.Anybody solve this problem ?
Anonymous
Jan 07, 2012Doesn't wotk with Perforce. Maybe its the charset setting but not enough info on how to fix this.
I set Charset to "Windows-1252" whilst the default choice in P4v says "Wester European (WinAnsi 1252)" though it is unchecked in the Connections tab of Preference of P4v.
Perhaps a step is needed for p4protect? Where's this documented?
Error message from FishEye:
Perforce Server Version: P4D/LINUX26X86_64/2010.2/347035 (2011/08/24)
Perforce Server Time: 2012/01/07 04:18:42 -0500 EST
Non-zero exit status determining latest revision: com.atlassian.utils.process.ProcessException:Non-zero exit code: 1 | Access for user 'NOTPUBLIC' has not been enabled by 'p4 protect'.
Error testing connection.
Unable to determine latest revision. No revision information was returned - check path exists, permissions and output encoding
Connection failed.
.
Anonymous
Jan 07, 2012Working now. Had to set password in lowercase. Forgot that's what Perforce uses here and otherwise the system login was being used it seems and it is uppercase. Well, "scanning" now. Not but like 20 files in this folder so not sure why this is taking >10 minutes. We'll see.
Anonymous
Jan 07, 2012I don't know what is happening. I see pv commands logged but no info shows when I try to review the repo. All I'm trying to do is get LOC by user for crying out loud. Maybe this next error is only in their UI and not what is wrong/working/running.
Looks like they used GWT to build this and some Google error is occurring (I hope they are not trying to actually call an external server. That will never work here.)...
Error
Got a suggestion or an issue?
Discuss it in our forums or visit our support website for other options.
Anonymous
Jan 07, 2012Does FishEye require me to first install Git? ???
Anonymous
Apr 07, 2012I got the error below. It turned out that P4TICKETS (nor HOME) environment variables were not set. As a result p4 login failed to create tickets and further operation failed. Setting them solved the problem.
Anonymous
Jul 24, 2012where did you set P4TICKETS and HOME, did fisheye need to be restarted to pick up the changes?