Build And Release Management

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

Parallel Multiplatform Builds

This is the coolest feature we have ever added since introducing the remote builds! Now it is possible to launch and run multiple builds on multiple hosts and platform in parallel. Parabuild ensures that all builds run against the same code base and have the same build number or product version.


Parabuild helps create a distributed build infrastructure that before could take you months and sometimes years now in a matter of minutes! Parallel builds are especially suitable for industries developing software that has to run on multiple platforms such as computer game development.

Applications of parallel builds are many. The most obvious include multiplatform building and testing here the build is considered clean and if it was successful on all platforms, and build acceleration that can be easily archived by moving parts of a whole build process to multiple host.

Finalizing Build Step

Parabuild 3.1 adds support for a special "finalizer" build step. This step will run in the end of the build sequence without regard to the outcome of the previous build steps. You can use this step to collect and deploy build results to a QA environment even if a previous step running developer unit tests has filed.

A leading build in a parallel build list is guaranteed that its finalizer step is run after dependent builds have finished. This allows for build and test acceleration via distribution of load to remote builders under Parabuild control.


Fine-Grained Scheduling

Now it is possible to cherry-pick a particular hour and run a daily or a nightly build even if there have not been new changes. This feature is useful when your process requires running a build at given time:

 

External URL Result Type

This feature allows an administrator to publish build results that are stored outside of Parabuild. A URL template supports build.name, build.id and build.number parameters: