• Support
• Documentation
• BuildMaster
• Core Concepts
• Promotion Workflow

Promotion Workflow

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.

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.

Multiple workflows may be defined for each application. Examples of alternate workflows may include:

• branched development
• emergency fixes
• different approval rules

Approvals

Approvals may be set-up at each step of the workflow. When an approval is configured for a step (Testing, for example), that approval must be met prior to promoting the build to Testing. Approvals may have any name, from "Approved by John Doe" to "Smoke Test Passed."

When an approval is created, it is set-up as either a User or a Group approval. User approvals must be approved by the associated user, while group approvals require that a certain number of users within that group submit approvals.

For example, if you want approval from a QA lead and 3 other testers before your build is promoted to Staging, you can set up 2 approvals in your Staging environment:

• User approval - assigned to the QA Team Lead
• Group approval - assigned to 3 users in the group QA Team

Notifications

If a user would like to receive a notification when he needs to make an approval, he may either:

• Subscribe to the "Approval Required" notifier
• Check the "My Approvals" link under the logon user name