Approve from the Pipelines list
Approve or reject a run that waits on a deployment approval without leaving the Pipelines page.
Availability
Who can use this: Release manager and Org admin. See Roles.
A run waiting on a deployment approval has the Awaiting approval status. You can answer it without leaving the page.
Where to open the dialog
- Table: the shield badge in the Events column, the Review badge in an expanded row's Events list, and the row's ... menu (Review deployment...) all open the same dialog. The menu also has Open in Gates, which opens the approval on the Gates page. An expanded row has no Approve or Reject button. If only your provider's required reviewers can answer and you cannot, the action bar has a Review on GitHub link instead.
- Phone: tap the shield badge on the run's third line to open the dialog, or expand the run and select Review.
The badge shows as soon as Prodgator has the pending deployment, even if the row still says Running. The job that waits for the approval shows Awaiting approval and a Review link. In the jobs table, that job's Environment, Deployment, Prodgator and External gates columns show its deployment environment, status and gates.
To answer several at once, use bulk approve and bulk reject on the Gates page's Awaiting approval tab.
The dialog
The dialog is titled Review deployment. It opens with Cancel, Reject and Approve; nothing is chosen for you. Its first line tells you which gate you are answering:
- Prodgator's protection rule decides the gate, not GitHub. Release policies or Prodgator approvers answer it.
- Prodgator's rule and the environment's required reviewers both apply: GitHub also waits on its reviewers.
- The environment's required reviewers: your review is submitted as your linked GitHub account, so link it first under Profile > Linked accounts. If your account is not one of the required reviewers, the dialog is read-only and the row has a Review on GitHub link.
You can add an optional note. A rejection takes the same note.
When an Enforce release policy decides the deployment, the dialog says so before and after you approve: Policy name decides this deployment, with the rule, its status and its reason. After you approve, the dialog stays open with Your approval is recorded and the policy's answer. If the policy errors or fails, and you hold the override permission and the organization allows it, the dialog offers Override. See Approve deployments. The comment Prodgator posts to GitHub names you and your organization, followed by the note.
If a compliance policy in Block mode governs the deployment environment, answering Prodgator's rule overrides that policy's decision. Compliance and Org admins can do it (a Release manager cannot), and the dialog asks for a reason of 10 to 500 characters. The reason is written to the audit log and sent to GitHub. See Compliance policies.
Related
- Approve deployments: both kinds of gate and what Prodgator posts to the provider
- Gates: the Gates page and bulk actions