Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
Version FishEye 1.6.1 build-325
FISHEYE_HOME /usr/local/fisheye/fisheye-1.6.1
FISHEYE_INST /usr/local/fisheye/fisheye-1.6.1
Java Version 1.5.0_16
Java Vendor Sun Microsystems Inc.
JVM Version 1.0
JVM Vendor Sun Microsystems Inc.
JVM Impl Version 1.5.0_16-b02
Java Runtime Java(TM) 2 Runtime Environment, Standard Edition
Java VM Java HotSpot(TM) 64-Bit Server VM
Operating System Linux 2.6.18-8.el5
OS Architecture amd64
Total Memory 552M
Free Memory 32MVersion FishEye 1.6.1 build-325 FISHEYE_HOME /usr/local/fisheye/fisheye-1.6.1 FISHEYE_INST /usr/local/fisheye/fisheye-1.6.1 Java Version 1.5.0_16 Java Vendor Sun Microsystems Inc. JVM Version 1.0 JVM Vendor Sun Microsystems Inc. JVM Impl Version 1.5.0_16-b02 Java Runtime Java(TM) 2 Runtime Environment, Standard Edition Java VM Java HotSpot(TM) 64-Bit Server VM Operating System Linux 2.6.18-8.el5 OS Architecture amd64 Total Memory 552M Free Memory 32M
Description
While testing a demo of Fisheye, I find that it's handling of branches and copies in perforce is a bit weaker than expected.
Because Perforce tracks a file relationships, a branch of a file can be created simply by running the
p4 integrate fromFile toFile
command.
This means branches occur and are tracked on per-file basis in Perforce.
It would be a major improvement in Fisheye if it also resolved branches on a per-file basis.
The changeset information you include in Fisheye clearly lists files that have branched, yet you do not resolve the branch history properly. For example in the attached screenshot I was surprised not to see a branch from a common ancestor and a sibling for the file being displayed. This file should not just go straight-line to a "head" revision.
To properly get the true branch relationships of files in perforce the "p4 integrated" and "p4 filelog" commands need to be used.
As I said, properly resolving and displaying branch relationships in Fisheye would be a MAJOR improvement.
Thanks,
Jeff.
Docs
https://www.perforce.com/perforce/doc.current/manuals/p4guide/chapter.codelines.html
