This documentation relates to 2.0.x
If you are using an earlier version, please view the previous versions of the Crucible documentation and select the relevant version.

Setting Up a Perforce Repository in Stand-Alone Crucible

To set up Perforce in stand-alone Crucible,

  1. Ensure that the Perforce executable file is on the system path, in the Crucible server's Environment Variables
  2. Start Crucible then open the 'Admin' menu by clicking the Administration link in the footer of the page.
  3. Under the 'Repository Settings' heading, click 'Repository List' in the left-hand navigation bar.
  4. The 'Repository List' screen opens.
  5. Find the Perforce repository plugin and click its Configure Plugin link.
  6. The 'Configure Plugin' screen opens. Click 'Add Repository'.
  7. The 'Add Repository' screen opens. Fill in the fields.
    || Field || What to enter ||

    Name

    Choose a unique name for the repository.

    Repository Server

    Enter the base URL and port for the repository, for example:
    example.com:666.

    Repository Path

    Add the path to your Perforce repository. For example: //depot/code/example/main.

    Perforce Username

    Enter the username of the Perforce account that Crucible will use. (optional)
    (info)
    Note that this account should only have read-only access to the repository.

    Perforce Password

    Enter the password of the Perforce account that Crucible will use. (optional)


  8. Click 'Save'. The view will return to the list of repositories.
  9. Your Perforce repository is now set up for Crucible. You will be able to select changesets from it when creating reviews.

(info) There is no 'initial scanning' required in this process, as stand-alone Crucible's access to Perforce is strictly on-demand. Data is not indexed, hence there is no scanning.
(info) For those who may be interested, Crucible executes the Perforce command-line tool to enable this functionality.

  • No labels



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Blog and update.

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