All releases of Parabuild

4.0.40

25 Jun 2010 09:19

Release Notes: Parabuild now supports continuous integration and release management for Mercurial.

4.0.0

01 Jun 2009 17:57

Release Notes: This major release introduces load balancing and failover for the build farm, significantly simplifies build infrastructure management, provides an extensive Web Services API, and adds over 40 new features.

4.0.0 RC 1 Build 1667

27 May 2009 08:44

Release Notes: This build introduces the ability to push sever upgrades to remote build agents. An extensive Web Service API to monitor build statuses and to report on build results was added.

4.0.0 Beta Build 1651

19 May 2009 07:54

Release Notes: The workspace is cleaned up on agent change. Builds assigned to a particular agent machine can be displayed. A group of builds can be stopped and resumed. system-wide, project, and agent variables can be made available to a version control settings template. Serialized builds can be queued if all agents are busy.

4.0.0 Beta Build 1627

24 Apr 2009 07:19

Release Notes: This build adds advanced load balancing for the build farm and sticky build agents to support large codebases. Subversion integration now accepts the certificate automatically when accessing HTTPS locations. (The error which produced the message, "Server certificate verification failed: issuer is not trusted," was fixed.)

4.0.0 Beta

13 Mar 2009 22:08

Release Notes: This release adds load balancing and failover for a build farm by providing clusters of build agents. It also includes Continuous Integration and build and release management for AccuRev, and many Web user interface enhancements.

3.2

06 Feb 2008 10:16

Release Notes: This release adds more then 70 new features and enhancements including online build logs, parallel builds, and automated merging for Perforce.

3.2 Beta

05 Sep 2007 15:28

Release Notes: This release adds automatic inter-branch merging (integration) for Perforce and over 50 enhancements to its build and release management, build telemetry, user interface, version control integration, and notification subsystems.