Fisheye / Crucible treats a file as binary that should be text

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)

1 answer

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 ( to overrule those settings. Dunno if there is something similar for SVN.

PS: maybe this could help you changing the filetypes in SVN:

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Thursday in Jira

Updates to give you visibility into what's coming in Jira Server and Data Center

Hello, Community! My name is Gosia and I'm a Product Manager on Jira Server and Data Center here at Atlassian. Since 2002 when we launched our public issue tracker, jira.atlass...

302 views 1 12
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you