e-volv

CI playbook

DeployVerification

After a deploy workflow succeeds, independently verifies that serving revisions, health endpoints, and client bundles match the built commit.

When a deploy workflow completes successfully, independently verifies that what is serving matches what was built: resolves deployed revisions or image digests, checks traffic routing, calls health endpoints, and confirms the served client bundle hash where applicable. Opens a P1 incident ticket on any mismatch. Configure your ticket integration and make sure the agent can reach your cloud CLI and service URLs.

Identifier
deploy-verification
Version
1.0.0
Steps
3
Triggers
1
  • deploy
  • verification
  • post-deploy
  • ci
  • reliability
  • health

When it runs

CI resultci_workflow.completed
Settle delay
60s after the event

Only when all hold

  • ciWorkflow.conclusion equals success
  • ciWorkflow.name contains deploy
  • actor.username not contains [bot]

The pipeline

The graph below is the one the workflow opens with in the builder — same steps, same layout, drawn on the same canvas. The run playing through it is a simulation; the branches and conditions are real.

  1. 01
    Deploy Workflow Completedtrigger

    The event that starts the run.

  2. 02
    Clone Deployed Branchgit.clone

    Shallow-clones the repository at the right ref.

  3. 03
    Verify Deploymentagent.run

    One agent works the task with its toolkit.

The agent

Deploy Verifier

Base type
Senior Developer
Temperature
0.2
Max iterations
35
Tools
6

Tickets · 2

  • list_ticketsList Tickets · read
  • create_ticketCreate Ticket · write

Terminal · 1

  • run_terminal_cmdRun Terminal Command · write

CI/CD · 1

  • get_ci_run_logsGet CI Run Logs · read

Filesystem · 1

  • read_fileRead File · read

Status · 1

  • update_statusUpdate Status · write