![]() |
![]() |
Now it is possible to go back in time and to re-run an arbitrary build. This feature can be used to produce QA builds, release candidates or release builds:

Parabuild 3.0 allows to configure build parameters that will be passed to the build script as shell variables:

The build parameters are entered when a build administrator requests the build to start. The parameter can be used by the build script to alter the build sequence. The "Start build" screen now allows entering a build note and requesting labeling/tagging if the build is successful. One of the uses of this feature is build promotion:

Build display groups allow to limit displaying build statuses to a configurable list of builds. This feature can be used to display build statuses on a per-project basis:

Now it is possible to navigate build changes, logs and results using "Previous" and "Next" navigation links:
This feature allows to query and to display changes between two builds:

A graph of successful vs unsuccessful tests enables you to quickly see if the team is getting better or worse at keeping the tests working over time:

Go go to System settings and enable RSS:

After that an RSS link is available on the build list page and on the detailed build status page:

Now a user that starts a build manually is recorded. This user also receives a build result notification even if user's changes do not participate in the build:

It is now possible to see a high level overview of the build statuses right in the right corner of your Windows system tray!

Parabuild 3.0 adds support for three version control systems: Sourcegear Vault, Serena ChangeMan Version Manager (PVCS) and MKS Source Integrity Enterprise.



