Overview

Perforce is a commercial, multi-platform SCM made by Perforce Software.

Requirements

Support for Perforce in pulse™ is built on top of the command line client p4. This client is available from Perforce for a wide range of platforms, and is distributed as a single binary file which can be easily installed on any machine. To use Perforce from your pulse™ server, ensure
that the p4 binary is installed on the host machine and is in the PATH for the pulse™ process.

Note that pulse™ personal builds requires perforce version 2004.2 or later.

Configuration

Perforce configuration in pulse™ uses the same terminology as the Perforce tools themselves. For further details about the configuration options, consult the documentation for p4.

Clients

The client specified for a Perforce project will not be used directly. This field specifies the name of a client specification to use as a template for pulse™ to create temporary clients when connecting to Perforce. Whenever pulse™ communicates with the Perforce server, it will create a temporary client for that purpose. The created client will have the same view of the depot (to use Perforce terminology) as the specified template client. However, the temporary client's root will be changed appropriately, and the client will be deleted when the interaction is complete. Using temporary clients in this way prevents problems arising from Perforce maintaining client state on the Perforce server.

If you do not have a suitable template client in Perforce, you can create one using your Perforce client. Any developer working on the code line should have a client suitable to use as a template. By keeping the template client in Perforce up to date with any changes to your source code layout, there is no need to modify your settings in pulse™.