Perforce case-sensitivity issues on FE 2.4 Upgrade

XMLWordPrintable

    • Type: Bug
    • Resolution: Fixed
    • Priority: High
    • 2.4.1
    • Affects Version/s: 2.4.0
    • Component/s: None
    • Environment:

      Fisheye/Crucible 2.4.0
      Perforce Repository

    • 3

      On the upgrade of Fisheye 2.4.0, Perforce repositories fail to index or have odd behavior indexing. Symptoms of this problem include:

      • Only some content being indexed and viewable in the repository source.
      • No content at all being indexed, and source repository shows no files in the UI.
      • Files are shown in the repository UI but they are all listed as deleted.

      Common errors in the log files include:

      2010-10-21 14:59:29,001 ERROR [IncrementalPinger1] fisheye.app P4Cache-getFileRevision - Could not determine revid for key project1/main/README.txt@2
      2010-10-21 14:59:29,001 ERROR [IncrementalPinger1] fisheye.app P4Cache-getFileRevision - Could not determine revid for key project1/main/TEST.txt@2
      

      After development investigation it appears that this is related to case-sensitivity issues as part of the 2.4.0 release.

            Assignee:
            Conor (Inactive)
            Reporter:
            Anonymous
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved:

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 4h
                4h