13-deploy-smoke

To automate final deployment and smoke test verification, execute the pipeline skill to run API smokes, connectivity gates, and health checks. The process requires explicit user approval before proceeding and automatically handles retries or rollbacks if verification fails.

A blocking verification gate in a deployment pipeline ensures a deployment meets all criteria before proceeding to the next stage. It requires explicit user approval and performs automated health checks, API smokes, and connectivity checks to validate success.

Deployment pipelines handle rollback when smoke tests fail by automatically reverting the deployment if necessary. The verification process performs API smokes and health checks, managing retries before initiating a rollback to ensure system stability.

Yes, you need a previous verification stage completed and its checklist approved before running smoke tests. The final deployment and smoke test verification process follows a prior stage to ensure all required standards are met before proceeding.

Yes, you can update changelogs automatically during deployment automation. The final deployment and smoke test verification process includes changelog updates alongside API smokes, connectivity checks, and health checks to maintain accurate deployment records.