BuildMaster Documentation

Deployment Windows

  • Last Modified: 2019-07-17

Deployment windows allow you to restrict the days and times that builds may be deployed. They can be used in conjunction with manual deployments to enforce existing policies, or as part of a continuous delivery pipeline to ensure deployments occur within known times. Like user approvals, a build may be forced into a stage even if it's not within the specified window. However, this requires a special action and a specific permission.

Configuring Deployment Windows

A deployment window consists of day of the week, as well as a start and end time.

Config Deploying Windows

When the end time is earlier than the start time, then the window will "crossover" into the following day. For example, specifying "Sundays after 11:00pm and before 2:00am" will create a three-hour window from Sunday at 11:00pm until Monday at 2:00am.

You can specify deployment windows on the edit pipeline page.

Deploying Windows set

When there are multiple deployment windows specified, they are treated like an "or" condition; that is, as long as one of the deployment windows is valid, then a deployment may proceed.

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 ce197caa on master