Dashboard > Pulse v2.0 > ... > Personal Build Client > Requesting Personal Builds > Information > Page Comparison
  Pulse v2.0 Log In | Sign Up   View a printable version of the current page.  
  Requesting Personal Builds
compared with
Current by Jason Sankey
on Nov 20, 2008 18:46.

(show comment)
 
Key
These lines were removed. This word was removed.
These lines were added. This word was added.

View page history


There are 1 changes. View first change.

 h2. Overview
  
 You request personal builds by [configuring|Configuring the Personal Build Client] 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 {pn} [Manual].
  
 {note:title=Personal Build Security}
 Before you can request personal builds, you must be granted permission by the administrator of your {pn} server. For more information, refer to the [Groups] page in the main {pn} [Manual].
 {note}
  
 h2. Usage
  
 {noformat}
 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
 -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
 {noformat}
  
 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>'.
  
 h2. Examples
  
 To execute a basic personal build:
  
 {noformat}
 $ pulse personal
 {noformat}
  
 To build project "my project", without putting this detail in a properties file (see [Configuring the Personal Build Client]):
  
 {noformat}
 $ pulse personal -r "my project"
 {noformat}
  
 To submit a patch containing only files "file1" and "file12":
  
 {noformat}
 $ pulse personal file1 file12
 {noformat}
  
  To submit a patch contining the changes in Perforce changelist 123:
  To submit a patch containing the changes in Perforce changelist 123:
  
 {noformat}
 $ pulse personal :123
 {noformat}
Zutubi wiki is Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.2.10 Build:#528 Nov 29, 2006) - Bug/feature request - Contact Administrators