personal builds :: Pulse feature tour
Personal Builds in Pulse allow you to test your changes before you commit them to your SCM server. Used properly, this feature can eliminate the angst of broken builds and associated team down-time.
Personal builds are run much like any other build, with a few important differences:
- The build directory is initialised to a replica of your own current working copy. Your outstanding changes participate in the build.
- If a personal build fails, no other developers are affected. You are able to fix your changes and retest them before committing them to the shared code base.
- Your personal build results are visible only to you, on a special "my builds" tab in your dashboard.
Combined with Pulse's ability to distribute builds across multiple platforms, personal builds give developers a powerful way to develop and test changes. The developer can work in their preferred environment and let Pulse handle testing across different platforms, all without tainting the shared code base.
my builds dashboard view tab
You can view your personal build results just like other builds using the Pulse web interface. Just browse to the "my builds" tab on your personal dashboard. All of the information normally captured by Pulse is available for personal builds.
Personal build client
Personal builds are submitted to Pulse using the personal build client. This is a simple command-line utility that is platform and environment independent. The client is incredibly simple to use: it will even self-configure the first time it is invoked in a working copy.
