Using Crucible to test the code review process

[jim]

Hi,

     I downloaded and installed Crucible to test it in our code review process.  We use ClearCase for our version control software and I have a couple of questions:

     1. Can I, and if so, should I connect Crucible to our production ClearCase system?

     2. If possible, will it affect ClearCase in anyway?

     3. If it is not possible (or if I should not connect to it), can I test Crucible in a standalone configuration?

BTW, we are looking to move away from ClearCase within the next six months.

Thanks,

Jim

[Felipe Kraemer]

Hey @jim,

Fisheye and Crucible used to support ClearCase repositories, but that was until version 2.7, according to this announcement. 

It is not natively possible to add ClearCase repositories into Fisheye/Crucible from version 2.8 onwards, which, on its turn, is a very old version of Fisheye and Crucible, and is also no longer supported because it reached the End of Life policy for support. The older Fisheye/Crucible supported in this present day is 4.1.

I've searched for third-party add-ons in our Marketplace but could not find any compatible with Fisheye / Crucible.

At the moment, your only options seem to be:

• Create your own SCM plugin
• Convert your ClearCase repositories someway to Subversion, Git, Mercurial or Perforce, which are the other SCM types supported by Fisheye and Crucible. 

This second option seems to be your best one, specially having in mind that you mentioned you intend to move away from ClearCase within the next six months.

I hope this information helps!

Felipe

[jim]

Thanks, we are planning to move off ClearCase, but that will take some time.  Can Crucible be used without connecting to a version control system?  Does it have a value if the code can be copied into it rather can pulling it from a system?

[Felipe Kraemer]

Hi @jim,

As can be seen in the Crucible and FishEye document, both of these products can run in complete isolation of the other, but they are distributed together, in a single package, and start as a single instance.

You just "unlock" the usage of one, or the other, or both, by configuring a valid license for each product in their corresponding License field, as can be seen in this image:

That being said, there are many ways of adding content to a Crucible review, as can be seen here:

Adding content to the review

Two of these options do not require having a repository added to the instance: "Pre-commit" patches and the "Attachments".

Maybe one of these two options suit your needs?

Regards,

Felipe