BuildMaster Documentation

Server

BuildMaster deploys your application releases to the servers that you configure.

A server can be physical (bare metal), virtual, or even nonexistent (i.e. one that you will provision later using Otter).

Adding Servers to BuildMaster

You can add a server using the web-based user interface (Servers > Add Server), or programmatically with the infrastructure API.

BuildMaster communicates with servers using the Inedo Agent (for Windows) or SSH/SFTP (for Windows and Linux).

Deploying to Servers

In addition to using Server Roles, there are two ways to deploy to a server:

Pipeline Stage Target

You can specify a list of servers as a stage target in a pipeline stage. When the release package is deployed to that stage, the stage target's deployment plan will be run against all those servers.

Servers and OtterScript

You can deploy to a server using a general block

            for server prod-hdars-sv1
            {
                Deploy-Artifact hdars-api-service
                (
                    To: C:\HDars\App\api-service
                );
            }            
    

Server vs Server Roles

Deploying to server roles can be helpful when you don't want to explicitly specify server names. For example, in a multi-tier application that's designed to run across multiple servers.

However, if your application has always been deployed to a specific server, and will be deployed to that specific server for the foreseeable future, there's not much value in creating a specific role for it. In fact, it may create confusion, as other users may be unfamiliar with the concept of roles.