You request personal builds by configuring the personal build client and then executing it using the "personal" command for the pulse script (pulse.bat) on Windows. For details about how to invoke the script, refer to Server Commands page in the pulse™ Manual.
|Personal Build Security|
Before you can request personal builds, you must be granted permission by the administrator of your pulse™ server. For more information, refer to the Groups page in the main pulse™ Manual.
personal <file> ...
Sends a personal build request to a pulse server. This involves updating
the current working copy, analysing any outstanding changes, forming a patch
file and sending the patch to the pulse server to execute a build.
Configuration is defined via properties files or command line arguments. The
configuration specifies connection details for the pulse server, along with
information about the project and build specification you wish to execute.
The SCM configuration of the project must match the working copy.
-r [--project] project : set project to build
-s [--server] url : set pulse server url
-u [--user] name : set pulse user name
-p [--password] password : set pulse password
-d [--define] name=value : set named property to given value
-q [--quiet] : suppress unnecessary output
-v [--verbose] : show verbose output
-t [--status] : show status only, do not update or build
To limit the personal build to only some of the changed files in your working copy, you can specify those files on the command line. For Perforce, you may also specify a changelist number using ':<changelist>'.
To execute a basic personal build:
To build project "my project", without putting this detail in a properties file (see Configuring the Personal Build Client):
$ pulse personal -r "my project"
To submit a patch containing only files "file1" and "file12":
$ pulse personal file1 file12
To submit a patch containing the changes in Perforce changelist 123: