Uploaded image for project: 'FishEye'
  1. FishEye
  2. FE-738

Improve handling of branching in Perforce

    XMLWordPrintable

    Details

    • Type: Suggestion
    • Status: Not Being Considered (View Workflow)
    • Priority: Medium
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: vcs-Perforce
    • Labels:
      None
    • Environment:

      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

        Attachments

        1. fe-738-p4v.png
          fe-738-p4v.png
          35 kB
        2. Fisheye Perforce Branch.jpg
          Fisheye Perforce Branch.jpg
          85 kB

          Issue Links

            Activity

              People

              • Votes:
                14 Vote for this issue
                Watchers:
                22 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Last commented:
                  5 weeks ago