Continuous Integration Features
You can use BuildMaster's repeatable deployment automation with your existing Continuous Integration suite, or
if you're not currently using CI, use BuildMaster's basic Build Automation features to get started.
Build Artifacts are a key aspect of reliable and repeatable software delivery, and are a first-class concept in BuildMaster.
Create any number of artifacts at any point in the build process.
Once a build artifact has been created, it can be deployed during any deployment plan.
Each artifact you create as part of the build and deployment process
is attached to the build, and may be downloaded by any user
with sufficient privileges.
Make TeamCity Builds Configurations easily selectable with a variable.
Simply hit a URL Trigger in BuildMaster to kick-off a deployment workflow.
Integrate with CI Servers
BuildMaster's CI Integrations can be used to communicate
with your existing continuous integration servers to...
- Create New Builds
- Wait until Build Completion
- Capture Build Output
You can also kick-off a deployment from CI using a
URL Trigger or the BuildMaster API.
Built-in CI Capabilities
If you don't have a CI server, BuildMaster's deployment plans can be easily configured to create and test builds.
These builds can then be triggered by source control check-in or scheduled to run at virtually any frequency (i.e. daily, hourly, etc.).
- Monitor multiple SCM paths
- Change quiet period
- Branched/multiple workflow support
Configure Source Control Providers with a rich user interface.
Browse for source control paths instead of having to type them in.
Easily apply labels, tag builds.
Use Variables to created Branched workflows for advanced build/deploy configuration.
Unleash all of the features in your source control client with Client Commands.
Source Control Integration
BuildMaster's Source Control Providers are easy to configure and use,
and allow you to use the same patterns and best practices regardless of your tooling.
You can easily switch and even set-up multiple source control providers for the same application.
BuildMaster offers a detailed view into each unit test, providing insight into specific test failures.
BuildMaster can prevent promotion of a build to an environment if any unit tests were run and have failed.
Several different test runners are available that can store your results automatically.
Use any command-line tool (custom or third-party) to generate and optionally transform into build reports.
Build Reports such as code coverage are stored with builds and can be easily accessed.
Add further verification to ensure builds aren't promoted that shouldn't be.