Integration With Version Control Systems

Parabuild supports the growing number of version control systems (VCS). Perforce, CVS, Subversion, ClearCase, Serena ChangeMan (PVCS), Borland StarTeam, Seapine Surround SCM, SourceGear Vault, Visual SourceSafe and MKS Source Integrity are currently supported.

Perforce

Parabuild supports Perforce:

Subversion

Parabuild supports Subversion:

CVS

Parabuild supports CVS:

The following features have been added to the version control integration subsystem in Parabuild 3.0.

Borland StarTeam

Support for Borland StarTeam has been added:

SourceGear Vault

Support for SourceGear Vault has been added:

Serena ChangeMan Version Manager (PVCS)

Support for Serena ChangeMan Version Manager has been added:

MKS Source Integrity Enterprise

Support for MKS Source Integrity Enterprise has been added:

 

An Ignore-List

All build configurations can now provide a list of paths for that a change in the version control system should be ignored. Changes in the files included into the ignore-list will not trigger the build:

 

Support For Module Aliases In CVS

CVS modules are supported.

 

An Option To Make Visual SourceSafe Files Read-Only After Checkout

Parabuild 3.0 adds an option for Visual SourceSafe to make files read-only after getting updating the local copy:

Support For Ignoring Arbitrary ClearCase Errors

Parabuild now supports ignoring arbitrary errors appearing in the ClearCase error log while requesting changes or updating the local copy. This feature may be useful is a user Parabuild runs under doesn't have privileges to access certain load paths:

 

Support For Multiple Branches In ClearCase

Multiple ClearCase branches are now supported:

Smart Synthetic Change Lists

CVS, ClearCase, PVCS, StarTeam and Surround are supported to allow painless integration of changes.

Build Labeling/Tagging.

If configured, Parabuild labels successful builds according to configured label name patterns.

Multi-Line VCS Repository Paths

Parabuild supports projects requiring multiple VCS depot paths.

File-System

File-system "version control system" is supported to allow tracking changes an launching builds based on changes in files.

Simplified Display Group Navigation

It is possible to select a particular display group with one click:

 

Integration With Cenqua FishEye

Parabuild 3.1 provides nice roundtripping from a build change list to viewing repository content usinng Cenqua's FishEye. Subversion and CVS build configurations allow you selecting eihter FishEye or ViewCVS/ViewVC:

 

Showing Current Build Number In Previous/Next Navigation

Parabuild simplifies navigation through build result by displaying the current build number: