Crucible 2.8 : What happens if I decide to stop using FishEye with Crucible

Crucible can be run as an application alone, without FishEye. However, if you decide to stop using FishEye with Crucible, you will lose certain functionality and will need to make configuration changes.

On this page:

How do I run Crucible without FishEye?

  • Have a valid Crucible license but not a FishEye license
    To run Crucible without FishEye, you need to have a valid Crucible license but not a FishEye license. Crucible will actually use a "light" mode of FishEye when you do not have valid FishEye license. Light FishEye is bundled with Crucible and does not need to be installed separately. For more information on Crucible with light FishEye, see How is Crucible without FishEye different from using Crucible with FishEye? below.

How is Crucible without FishEye different from using Crucible with FishEye?

The following changes in functionality will occur if you use Crucible without FishEye (i.e. use Crucible with "light" FishEye).

Conducting Reviews

  • When using Iterative Reviews in Crucible, you will not be prompted when a new version of a file is available.

Viewing Repositories/Files

  • Files and changesets displayed in activity streams (e.g. the dashboard activity stream) will not render as links to the relevant files/changesets.
  • You will not be able to see your content roots and repositories associated with projects.

Charts

Can I still use lightSCM plugins with Crucible?

Legacy "lightSCM" plugins, like the Crucible Subversion SCM plugin, will still work with Crucible. However, we recommend that you use the "light" FishEye implementation that is bundled with Crucible, as it supersedes the lightSCM plugins.

For more information, please read this FAQ: Advantages of Native Repository Access over lightSCM plugins.