Approve from the Pipelines list
Approve or reject a run that waits on a deployment approval without leaving the Pipelines page.
Availability
A run waiting on a deployment approval has the Awaiting approval status. You can answer it without leaving the page.
Where the buttons are
- Table: the row's ... menu has Approve deployment... and Reject deployment..., and Open in Gates, which opens the approval on the Gates page. An expanded row puts Approve and Reject on the job that waits, one pair for each waiting deployment environment (named on the buttons when there is more than one). A waiting deployment Prodgator cannot match to a job puts its pair first in the action bar instead, before the run's links, Re-run failed jobs and Cancel run. Under the bar, an Approval needed line names each waiting deployment environment, linked to it on the Gates page, and what its approval waits on.
- Phone: tap the shield button on the run to open the approval sheet, or expand the run for the same buttons as the table.
The buttons show 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.
To answer several at once, use bulk approve and bulk reject on the Gates page's Awaiting approval tab.
The dialog
The dialog tells you which gate you are answering:
- Awaiting Prodgator Policies: Prodgator's own protection rule on the GitHub environment, while release policies decide it.
- Awaiting approval in Prodgator: the same rule when no release policy decides it, so someone approves it in Prodgator.
- Awaiting approval from GitHub 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, use Review on GitHub.
You can add an optional note. 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. Only an admin can do it, 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