I'm using the most recent versions of FishEye and Crucible together on CentOS 7.1. Per the documentation, I downloaded the p4 binary and put it in:
Despite that, when I try to add the config, I get this error:
Errors: /opt/fecru-3.10.3/bin/p4home does not exist or can not be accessed. P4 executable does not exist at configured location: /opt/fecru-3.10.3/bin/p4home, using 'p4' instead, make sure it is on your PATH.
I even went so far as to mark the folder 777 to see if it was a permissions problem. No luck. I can't explain why it can't find the folder, much less the binary, when I can see it myself. Apologies for the file directory gore and general sloppiness in the setup, this is a quick and dirty process to figure out what the installation process is like.
Hi @Parham Gholami,
It seems you configured P4 binary path in FishEye to /opt/fecru-3.10.3/bin/p4home - I'm not clear, is /opt/fecru-3.10.3/bin/p4home a folder containing p4 binary or a full path to p4 binary?
In typical configuration you would download p4 binary to some folder and store them under original p4 name, e.g.
grant it executable permissions
chmod a+x /opt/fecru-3.10.3/bin/p4home/p4
verify if it can be executed
$ /opt/fecru-3.10.3/bin/p4home/p4 -V Perforce - The Fast Software Configuration Management System. ...
Note those steps should be performed on behalf of the user running FishEye - if you use different user you may find out FishEye user doesn't have sufficient permissions to run p4 binary.
Finally, configure FishEye with the full absolute path to p4 binary (setting it to owning folder is not going to work), i.e.
If this still doesn't help check your logs (FISHEYE_INST/var/log/atlassian-fisheye-DATE.log) for more details.
Hope that helps,