You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
We are trying to use Fisheye / Crucible to conduct a code review on some automated test scripts. These scripts have the extension .scs. Fisheye/Crucible thinks these are binary files and therefore will not produce a diff, only offers to let you download the two revisions. Surely there is some way to tell the application to treat files with a given extension as a text file?
There are a couple of articles in the knowledge base regarding text files being treated as binary, but one pertains to Perforce which we aren't using (we use SVN) and the other pertains to upgrading from a previous release which we haven't done. However, I still tried adding scs to the
FISHEYE_HOME/raw-mime.types file but this had no effect.
We are running Version:2.6.3 Build:20110809072850 2011-08-09)
I guess that FeCru asks SVN for the file type. So maybe you could introduce your .scs files as textfiles to SVN.
I am not using SVN but had a similar problem with ClearCase. Support told me, that FeCru will use the repositories' filetypes.
For CC there is a types.txt (http://confluence.atlassian.com/display/FISHEYE/ClearCase#ClearCase-TextTypes) to overrule those settings. Dunno if there is something similar for SVN.
PS: maybe this could help you changing the filetypes in SVN: http://stackoverflow.com/questions/73797/how-do-i-tell-subversion-to-treat-a-file-as-a-binary-file