Dashboard > Pulse v1.2 > ... > Project SCM > Perforce
  Pulse v1.2 Log In | Sign Up   View a printable version of the current page.  
  Perforce
Added by Jason Sankey, last edited by Daniel Ostermeier on May 26, 2006  (view change)
Labels: 
(None)

Pulse Manual Index

Overview

Perforce is a commercial, multi-platform SCM made by Perforce Software. 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.

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.

port

This value is analogous to the P4PORT environment variable. It should contain the server name and port for the Perforce server, separated by a colon. Either field may be blank, in which case the default is used ("perforce" and "1666" respectively), but the colon should always be given.

This field is required.

Examples

To specify the default explicitly:

perforce:1666

Port "1234" on the local machine:

:1234

user

Analogous to the P4USER environment variable. The login name to use for connecting to the Perforce server.

This field is required.

Password

Analogous to the P4PASSWD environment variable. The password for the user specified above.

This field is not required.

Client

Similar to the P4CLIENT variable, although the client specified 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™.

This field is required.

Examples

example-trunk

monitor

The monitor field defines whether or not the configured SCM will be monitored for changes. By default, this value is set to true.

Zutubi wiki is Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.2.10 Build:#528 Nov 29, 2006) - Bug/feature request - Contact Administrators