Crucible evaluation/Perforce - is it easy to uninstall?

[Andrew DeFaria]

We would like to evaluate Crucible. We use Perforce. I'd like to set this up looking at our production Perforce instance but I want to make sure that if we want to go with something else, we can easily uninstall this without leaving crud in production. Is this doable?

[Andrew DeFaria · Accepted solution]

Yeah but does Crucible create any Perforce things that would need to be cleaned up if we decide to uninstall? Perforce's own Swarm creates some Perforce metadata and we were wondering if this does too.

[Tom Davies]

No, FishEye/Crucible's access to Perforce is strictly read-only.

[Tom Davies]

Hi Andrew,

FishEye/Crucible lives entirely in two directories -- the directory you create when you unzip the download (FISHEYE_HOME) and the directory where it keeps its data (FISHEYE_INST). In fact if you don't set a FISHEYE_INST environment variable all the data will be written into FISHEYE_HOME. That makes upgrades more complicated, but is fine for evaluation.

To uninstall all you need to do is delete those directories.

Please let us know if you have any other questions.

Thanks,

Tom