When adding or managing a Perforce repository, you must:
- Define repository details, as described below.
- Set Fisheye's repository options.
- Please refer to Supported platforms to see the version of Perforce that is required by Fisheye.
- You must have set the path to the Perforce executable in Fisheye before you can add Perforce repositories.
Perforce repository setup
- Click the 'cog' menu in the Fisheye header, and choose Administration (you'll need to be logged in as an administrator to see this link).
- Click Repositories (under 'Repository Settings').
- Click Add repository.
- Complete the wizard:
A name for this repository. The name may contain alphanumeric, underscore, '-' or '.' characters and its length must not exceed 100 characters.
Note that a repository name is different from its key. See Renaming a repository for details.
A short description of this repository.
The name of the server which provides the Perforce repository.
The path within the Perforce depot that you want Fisheye to index. You would normally put the depot path here, e.g.
(Optional) The port the server is listening on. Fisheye will default to the standard Perforce port (1666) if you do not specify a value here.
|The account that Fisheye should use to connect to the Perforce repository.
|The pasword for the account that Fisheye should use to connect to the Perforce repository.
Controls how many changelists Fisheye will fetch from the depot in one batch. Larger values can reduce the time it takes for Fisheye to scan your repository for changes, but use more memory. The default is 400. The minimum being 1. This field only accepts positive whole numbers.
Fisheye uses the P4
P4 Operation Timeout
Sets the timeout value that Fisheye imposes on P4 operations. Operations which exceed this value are terminated. The default for most operations is 10 minutes.
If set, this allows Fisheye to throttle how many connections it makes per second to the Perforce server. The default is blank (do not throttle). You may enter fractional values such as 2.5.
The character set used to interpret and display text files.
This field indicates whether the Perforce Server is running in internationalized mode.
When true, Fisheye will not scan Perforce Labels for Fisheye tag information.
This field indicates whether the Perforce Server metadata is case sensitive. You should set this to 'false' for servers running on Windows platforms.
Disable Multiple Print
When Fisheye needs file content from Perforce, it uses a p4 print operation. Normally Fisheye will request multiple files in one operation but this can cause problems in some Perforce instances. Set this value to true to disable printing multiple files in one operation.
If you wish to set this, please enter a changelist number. If set, the revision number from which Fisheye will start indexing the repository. The default is to start scanning from the first revision in the repository.
When a Start Revision is set, this setting controls how Fisheye establishes the initial state of the repository.
The credentials to use if your repository requires authentication.
Store Diff Info
Enable this option if you are using the Subversion or Perforce SCM systems and making use of per-author line counts. Otherwise, enabling this option is not necessary. Read more information
Controls whether Fisheye will immediately enable this repository, which starts the initial scan. If you wish to do some further configuration before the scan starts, then select 'No'. You can enable a repository later from the Repository List.