“...we can now react at the speed of business...” “...all of my projects are building wonderfully and are fully integrated into deployment...” “BuildMaster is absolutely swell!” “BuildMaster is a great tool for automating the build process, but stands head and shoulders above other tools...” “...manual, error-prone deployments are a thing of the past...” “...we implemented a *real* deployment process...” “BuildMaster made us re-think what proper deployment is...” “...this is a very solid piece of software!” “...our confidence in the reliability and repeatability of the deployment process has been restored...” “...extremely capable software, especially in an enterprise environment...” “...it's 2:45 AM your time?! Do you guys never sleep?” “...BuildMaster makes sense of incremental builds and their very liquid feature sets...” “...the best thing since sliced bread when it comes to managing projects and their environments...”

BuildMaster Extensions

 
 
 
ExtensionSubversion
AuthorInedo
Tags[edit]
Current Release3.1 (notes)

Please refer to the documentation for information about how to manually install an extension in BuildMaster.

Previous Releases

 
3.0 1/7/2012Download v3.0
2.6 10/10/2011Download v2.6

Subversion Extension

The Subversion extension provides integration with Subversion source control repositories.

Subversion Prerequisites

On Windows systems, the Subversion extension will use the SharpSvn client for communicating with repositories, so no additional software is required. On Linux, the svn command-line client is required. Note that the command-line client may also be used on Windows if configured in the Subversion Provider.

Source Control Actions

The Get Latest action is fully supported by the Subversion provider. However, since Subversion does not have a concept of labels, the Get Labeled and Apply Label actions are not supported.

Tagging in Subversion

The Branch action can be used to tag source code in a repository by copying it to another path.

Branch Action

Select the path to tag in the Source Path field, the tag path in the Target Path field (using the BuildMaster %RELNO% and %BLDNO% variables), and optionally a comment describing the action.