CRC-5 - Perforce client checked-in text file but shown up as 'binary'

Product: Crucible

Environment

Operating System  
Affect Version/s  
JVM  
Database  
Application Server  

Error Message


Symptom

FishEye and Crucible identify a text file as binary in Perforce repository. (Crucible and FishEye share same data directory)

Diagnostics/Test

Confirm with customer that the file is not binary.

Root Cause

FishEye can communicate with any Perforce server, but it needs to use the p4 command-line client to do so. This is a bug with P4 client older than P4 client (2006.1).

Solution

Upgrade to a recent P4 client (2006.1 onwards) and set filelog limit to 100, 50 or even 10 (by doing so, will impact performance significantly) in FishEye administration page.

Labels