Setting up a Perforce repository in Crucible alone

This page describes how to configure Crucible access to Perforce repositories.

Crucible SCM plugins superseded by Native Repository Access

Crucible now ships with native repository access, which allows you to connect to repositories without having Fisheye integrated with your Crucible instance. Crucible SCM plugins will still work, but we recommend that you stop using them in favor of native repository access. See What happens if I decide to stop using Fisheye with Crucible for instructions.

On this page:

Setting up a Perforce repository using native access

To set up native access to a Perforce repository:

  1. Go to the Crucible admin area.
  2. Click Repositories (under 'Repository Settings'), and then Native Repository Access (if necessary).
  3. Click Add Existing...
  4. Refer to Perforce in the Fisheye documentation for detailed information about completing the wizard.

Setting up the Crucible Perforce SCM plugin

This section describes how to configure the Crucible Perforce SCM plugin to access Perforce repositories.

To set up Perforce in Crucible alone:

  1. Ensure that the Perforce executable file is on the system path, in the Crucible server's Environment Variables
  2. Start Crucible and go to the admin area.
  3. Click Manage Add-ons (under 'Systems Settings').
  4. Find and click on the Crucible Perforce SCM Plugin (click Show System Plugins) and then click Configure.
  5. Click Add a repository and complete the form:

    1. Name: Choose a unique name for the repository.

    2. Repository Server: Enter the base URL and port for the repository, for example:
    3. Repository Path: Add the path to your Perforce repository. For example: //depot/code/example/main.
    4. Perforce Username: Enter the username of the Perforce account that Crucible will use. (optional). Note that this account should only have read-only access to the repository.
    5. Perforce Password: Enter the password of the Perforce account that Crucible will use. (optional)
  6. Click Save.

Your Perforce repository is now set up for Crucible. You will be able to select changesets from it when creating reviews.


  • There is no 'initial scanning' required in this process, as Crucible's access to Perforce (when running alone) is strictly on-demand. Data is not indexed, hence there is no scanning.
  • Crucible executes the Perforce command-line tool to enable this functionality.
Last modified on Jul 31, 2018

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.