BuildMaster Documentation

Getting Started with BuildMaster

  • Last Modified: 2020-06-26

BuildMaster lets you release your software reliably, to any environment, at whatever pace the business demands.

Build a self-service release management platform by allowing different teams to manage their own applications and deploy to their own environments.

Start simple and then scale to thousands of servers and the cloud.

Here is a Short Guide to get you Started Quick:

In this tutorial, you’ll learn how to create an ASP.NET CI/CD application and deploy it using BuildMaster’s CI/CD pipeline.

View the full step-by-step tutorial here.

BuildMaster will install on any supported version of Windows; simply download, and click through the installer to get BuildMaster up and running in minutes. Through the installer, you select the edition you wish to install; a trial, the free edition, or enter a license key. Review the step-by-step Installation Guide for details as to what's happening behind the scenes.

Agents and Servers in BuildMaster

To deploy releases to your servers, BuildMaster needs to be able to communicate with those servers over a fast and secure channel. There are a few options for doing this.

The Inedo Agent is generally the best way to communicate with a Windows server. It's a lightweight, highly-optimized agent that is simple to deploy and upgrade, but is also backwards- and forwards-compatible to minimize change risks. Alternatively, BuildMaster can use PowerShell Remoting to communicate with Windows servers; however, this is generally slower and less resilient than the Inedo Agent protocol.

To communicate with Linux servers, BuildMaster uses SSH and SFTP, and if you're using BuildMaster to interact with the server it is installed on, you can just set it up using a local agent.

Is this documentation incorrect or incomplete? Help us by contributing!

This documentation is licensed under CC-BY-SA-4.0 and stored in GitHub.

Generated from commit 99e6640e on master