Version 5

v5 is fully supported; bug fixes will continue to be shipped in the 5.8 release, and we will continue to maintain earlier v5 releases to resolve any critical or security issues discovered for users who cannot yet upgrade to 5.8

The central theme of v5 is modern application release automation. This means modernizing some of our approaches to problems (for example, pipelines as code) and creating more integrations that help BuildMaster fit even nicer in enterprise DevOps toolchains.

Version 4

v4 is semi-retired, which means that we will provide very limited support to v4 users who have not yet upgraded, and will provide assistance in performing upgrades. However, we will no longer ship maintenance releases, patches, or other changes.

The central theme of v4 was usability, not just in making things look nicer and be easier to use, but in improving our existing features, making them more flexible, and easier to discover.

Version 3

v3 is semi-retired, which means that we will provide very limited support to v3 users who have not yet upgraded, and will provide assistance in performing upgrades. However, we will no longer ship maintenance releases, patches, or other changes.

Although there was no central theme to BuildMaster 3.x releases, we made significant performance and architectural improvements, and solidified a lot of our existing features while adding a few more.

Version 2

v2 has been retired and is no longer supported.

The main focus for BuildMaster 2.x releases was new features. We introduced a whole lot of them, including an installer, Promotion Requirements, chained builds & deployments, Change Controls, Server Groups & Clustered Deployments, Triggers, the API, the the SDK, the Extension Gallery, and a free edition.

Version 1

v1 has been retired and is no longer supported.

Long before "DevOps" and "continuous delivery" entered the general lexicon, we shipped BuildMaster 1.0. It was rough around the edges yet functional. We learned that there was definitely a demand for this type of product, but that it needed far more features to solve complex deployment and delivery scenarios.