A promotion workflow represents the sequence of environments that a build must be promoted to prior to being considered deployed and "in production." It also defines the approvals and requirements necessary for promotion.
Workflows can be defined such that approvals are required before a promotion is allowed. Approvals can be targeted to a specific user or a group of users such as testers.
BuildMaster allows you to create specialized workflows that describe the transition or promotion of your software through its testing environments and ultimately into production.
Generally your applications will use the same workflow for every release, but occasionally there may an emergency fix that requires a separate workflow that defines an immediate deployment to your production environment.
A detailed history of all approvals is maintained by BuildMaster, so there will always be a record of promotion approvals.
Any user of the system with the appropriate privileges can force the promotion of a build regardless of approvals.
Similar to the approval process, a Promotion Requirement is a step added to a deployment plan workflow that will block promotion to a specific environment until the requirement has been deemed "completed". BuildMaster includes a number of built-in promotion requirements, and they are an extensibility point as well.
Ensure that all issues are closed or resolved before a promotion to the next environment.
BuildMaster can prevent promotion of a build to an environment if any unit tests were run and have failed.
Have BuildMaster verify that an application is ready for promotion to a specific environment by using your own custom tool or integrated Promotion Requirement.
