すべてのバージョン
Crucible 4.2 DocumentationCrucible 4.1 Documentation
Crucible 4.0 Documentation
More...
This page contains instructions on how to configure the Crucible Perforce SCM plugin to access 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 a working version of standalone FishEye. Crucible SCM plugins will still work, but we recommend that you stop using them in favour of native repository access. See What happens if I decide to stop using FishEye with Crucible? for instructions.
On this page:
To set up Perforce in stand-alone Crucible, 名前 Choose a unique name for the repository. Repository Server Enter the base URL and port for the repository, for example: Repository Path Add the path to your Perforce repository. For example: Perforce Username Enter the username of the Perforce account that Crucible will use. (optional) Perforce Password Enter the password of the Perforce account that Crucible will use. (optional)
|| Field || What to enter ||
example.com:666.
//depot/code/example/main.
Note that this account should only have read-only access to the repository.
注意
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.
Crucible executes the Perforce command-line tool to enable this functionality.