Dashboard > Pulse v1.2 > ... > Personal Build Client > Requesting Personal Builds
  Pulse v1.2 Log In | Sign Up   View a printable version of the current page.  
  Requesting Personal Builds
Added by Jason Sankey, last edited by Jason Sankey on Oct 30, 2006  (view change)
Labels: 
(None)

Pulse Manual Index

Overview

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.

Usage

personal
personal <file> ...
personal :<changelist>

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.

Available options:
-r [--project] project    : set project to build
-b [--specification] spec : set build specification 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>'.

Examples

To execute a basic personal build:

$ pulse personal

To build specification "continuous" of project "my project", without putting these details in a properties file (see Configuring the Personal Build Client):

$ pulse personal -r "my project" -b continuous

To submit a patch containing only files "file1" and "file12":

$ pulse personal file1 file12

To submit a patch contining the changes in Perforce changelist 123:

$ pulse personal :123

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