Fisheye - how we do save/preserve local changes to config files between updates

Al Lines

Fisheye

We have made enhancements to the files used for things like syntax checking to aid code reviews. These all work.

However when we upgraded Fisheye the changes were lost, as the application overrode the changes with the default set.

Is there a way to preserve our enhancements? E.g a folder where these are retained? Or some upgrade setting we missed? Or is this a defect in that it just applies its own files regardless.

Location of the files in question is:

C:\Atlassian\fecru\

Examples where we have updated are the filename.map, typescript.def

TIA

Al Lines

Had a reply from Atlassian directly:

"In general, any customisations added to the installation directory (FISHEYE_HOME) do not survive upgrades, since the new code/binaries for the new version will replace them.

If you would like to preserve your customisations between upgrade, you can add those files in the Fisheye data directory (FISHEYE_INST) which is (and should be) persistent between upgrades."

To help: Fisheye folder layout

So we have added our customisation to the directory FISHEYE_INST which in our case is  E:\ProgramData\Atlassian\Application Data\fecru

And then created in our case, a directory syntax under this and put the files there.

More to assist others on syntax in particular in Defining your own syntax highlighting in Crucible or Fisheye