BuildMaster Documentation

Environments

Environments are where you deploy an application to. Environments help you manage and structure your applications as your organization requires. You can assign restrictions, privileges, and approvals to individual environments as warranted for enterprise security and compliance needs.

Environment Structure

An environment is a logical grouping of servers, and generally describes one stage of the development process (development, testing, QA, etc.). In BuildMaster, there is no strict enforcement of how environments are set-up and defined. Deployment Plans are associated with zero or more environments, and are where you deploy an application to.

BuildMaster comes with three, built-in environments that represent a very simple pipeline: Integration, Testing, and Production. You can create, rename, and delete environments as needed.

Environments generally serve two key purposes:

  1. Pipeline definition - Where you target a deployment plan, ie. sequence of environments that changes must be tested in prior to productions.
  2. Security - privileges may be defined by environment. As such, access to things that are tied to a specific environment (production configuration files, deployment plans, etc), may be revoked.

Multiple Environments per Server

You can associate a server with more than one environment, though it's generally not recommended because it may create unexpected behaviors for other users in your organization.

Also, both sets of grants and restrictions will be applied, and if they overlap (one environment grants some things, while the other denies other things), then that will yield unpredictable and ambiguous behavior.