Home | Clover | Clover.NET | FishEye | Crucible | Support | Account | Download | Buy Now

Starting Points

Read the Crucible's features guide to understand how Crucible can benefit you.

To run Crucible you need a FishEye compatible source code repository setup. At the present time that is CVS, Subversion, or Perforce. The Crucible documentation therefore incorporates the FishEye documentation.

Read the Quick Start Guide if you are installing Crucible for the first time.

For Crucible troubleshooting information, see the FAQ or the Online Forums.

Quick introduction

Crucible is a tool that facilitates code review. It can be as valuable to organizations that already have a formal inspection process as it is to teams that don't review at all.

Regular peer review is a proven process with demonstrable return on investment. The benefits vary from team to team but commonly include:

  • Early bug and defect identification.
  • Sharing expertise and encouraging knowledge transfer.
  • Improving system wide knowledge.
  • Encouraging adherence to internal standards and style conventions.
  • Identifying individual strengths and weaknesses.

One of the less apparent, but nonetheless important, benefits that comes from a transparent code review process is that quality improves simply from the knowledge that code may be critically reviewed. Developers take more care with style, readability, comments, and commit messages because their peers are going to see it.

Despite these and many other clear benefits, code review is often seen as "impractical on time sensitive projects", "only valuable in large teams working on mission critical applications", or at worst "a total waste of time foisted on developers by management". Formal code review can feel like an expensive use of time, because the review process can be:

  • burdened by excessive paperwork and other administration
  • can interrupt your current task and make you less productive
  • include meetings where participants fail to prepare for and become walkthoughs rather than critical review, and
  • an ego battle or point scoring exercise dominated by a vocal minority.

These issues do not affect the immense potential value of code review, they are simply problems with some review processes. Crucible's mission is to streamline the process aspects so development teams can access the benefits. Crucible achieves this by:

  • making reviews asynchronous
  • bringing reviewing to your desk (wherever that might be)
  • eliminating most of the administration
  • limiting the ability for individuals to dominate the dialogue
  • providing an archival record of reviews

Crucible increases the quality, quantity, and frequency of code reviews thereby reducing bugs, helping knowledge sharing and fundamentally improving system quality.