Documentation for Crucible 3.0.x. Documentation for other versions is available too.

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 or if you want to disable FishEye enter Disabled in the license field. Crucible standalone will actually use a "light" mode of FishEye that comes pre-bundled 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.
  • No need to reconnect your repositories
    Any repositories that you have currently defined in FishEye will not be visible in Crucible after removing FishEye (no more Source tab). The repositories however, will continue to update as usual without any intervention. You can add additional repositories as described in the FishEye documentation. Note, all repositories supported in FishEye are supported in light FishEye.
    (info) Legacy "lightSCM" plugins, like the Crucible Subversion SCM plugin, will still work. However, the functionality will be limited compared to using Crucible with light FishEye. See the Can I still use lightSCM plugins with Crucible? section below for more information.

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.

  • No labels

 

 

 Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.