D5: Deploy www with a smoke test and rollback #73

Open
opened 2026-11-09 17:07:10 +00:00 by claude · 1 comment
Member

Create the first delivery pipeline: a manually triggered deploy of a chosen www image SHA, a post-deploy smoke test (home page, members page, and health), and one-step rollback to the prior SHA.

Payments are live, so test against non-mutating endpoints only, and never send test charges or webhooks to production.

Acceptance: a deploy is done through the workflow and a rollback is rehearsed, both with Eric watching. A failed smoke test is clearly reported.

Depends on: P3, D4.

Create the first delivery pipeline: a manually triggered deploy of a chosen www image SHA, a post-deploy smoke test (home page, members page, and health), and one-step rollback to the prior SHA. Payments are live, so test against non-mutating endpoints only, and never send test charges or webhooks to production. **Acceptance**: a deploy is done through the workflow and a rollback is rehearsed, both with Eric watching. A failed smoke test is clearly reported. Depends on: P3, D4.
claude added this to the CI/CD 4: Continuous delivery milestone 2026-11-09 17:07:10 +00:00
claude added the cicd
priority
high
labels 2026-11-09 17:07:10 +00:00
claude added this to the CI/CD Roadmap project 2026-11-09 17:07:33 +00:00
Author
Member

Update from D3 (#71), decided 2026-11-10: this pipeline is a manually triggered workflow_dispatch workflow with the www image SHA as its input. It deploys through the existing www Ansible role, run on the deploy runner from D4 (#72), not on the shared runner. Rollback is the same workflow with the previous SHA. Hand-run ansible-playbook stays the fallback. Nothing deploys automatically on push.

Still depends on P3 (#63) and D4 (#72).

— eom-cicd-roadmap

**Update from D3 (#71), decided 2026-11-10:** this pipeline is a manually triggered `workflow_dispatch` workflow with the www image SHA as its input. It deploys through the existing www Ansible role, run on the deploy runner from D4 (#72), not on the shared runner. Rollback is the same workflow with the previous SHA. Hand-run `ansible-playbook` stays the fallback. Nothing deploys automatically on push. Still depends on P3 (#63) and D4 (#72). — eom-cicd-roadmap
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DevOps/software-infrastructure#73