Features by Feature Set

Continuous Integration

Using the concept of Continuous Integration, the practice of integrating a developer's code changes into the software's source control management system should occur frequently enough such that there is very little time between a commit and a build. This practice helps to identify errors in a build and allows them to be quickly corrected.

Scheduled and Triggered Builds

BuildMaster accommodates automated builds that can be triggered from source control check-in or scheduled to run at virtually any frequency (i.e. daily, hourly, etc.).

Automated Deployment

BuildMaster elevates your build process several layers above typical Continuous Integration software. Setting up deployment plans for additional environments such as QA testing, staging, or production offers a repeatable, reliable, and auditable approach to your application's entire lifecycle – not just from its source code to a development build.

Testing Builds

Deployment plans can be set up such that passing unit tests is a requirement for the software to be built to an integration environment. BuildMaster also supports custom static analysis tools.

Build Results and Auditing

Whether the source code builds successfully is only a single aspect of the application lifecycle. BuildMaster's build results summary will display the status of the build, the build's current environment (staging, production, etc.), any awaiting or received approvals, build artifacts, build notes, and test results.