Build And Release Management

The following features have been added to the build management subsystem of the server:

Manual Builds

Parabuild 3.0 adds support for manual builds. As name implies, manual builds run on the build administrator's request. Manual builds may be suitable for producing builds off a short-living patch branch.

An Ability To Re-Run An Arbitrary Build

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:


 

Publishing Build Results

This feature allows an administrator to publish results produced by a build run and make them downloadable through the top navigation menu. An administrator can add build result groups, edit and delete them:

Once build results groups are defined, it is possible to publish build results right off the build results page. Also, new build results page allows to delete selected build results:

 

Automatic Deletion Of Old Build Results

Now it is possible to set Parabuild to delete archived build results that are older than given number of days automatically. This feature can be used to reduce disk space occupied by build results. Build results can be pinned to avoid automatic deletion.:

Build Parameters

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:

 

Product Version Templates And Counters

Parabuild supports generating product versions using flexible version templates and manually or automatically incremented counters:

Once version counter is defined and enabled, Parabuild will make it available on build start screen. Generated versions are recorded. Build scripts can access the generated version through the shell variable PARABUILD_VERSION.

An Ability To Disable A Build step

Build sequence configuration now allow to disable a particular build step without deleting it.

An Ability To Continue Build If A Build Step Failed

Some build configurations require to continue building if a build step failed. For instance, an automated test may fail but your quality assurance group still would like to test the results of the build.

 

Regex In Success And Failure Patterns

In addition to plain sub-string search, Parabuild 3.0 supports regular expressions in success and failure patterns. This allows for more fine-grained recognition of the successful and failed builds based on the content of the build logs.

« New features in accessibility