Skip to content

Dogfood: Tier 4 deploy canary (long-lived — do not merge or close) #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
RollNuts wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Dogfood: Tier 4 deploy canary (long-lived — do not merge or close) #13

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions docs/dogfood/tier4-canary.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
# Tier 4 deploy canary

This file exists so a long-lived pull request can carry a **fresh head SHA** for the
post-deploy Tier 4 smoke check.

The smoke sends a synthetic `check_suite` for this PR's head and then waits for a
`Veripsa` check to appear on that exact SHA. It needs a PR that stays open and whose
head can be moved cheaply.

**Why this repository rather than `veripsa-dev`:** the durable webhook inbox drains
per-account round-robin. A canary living in the same account as the busiest
repositories waits behind that account's traffic, and a deploy's own restart makes
the queue worse — so the canary timed out on deploys that had in fact succeeded.
Moving it to a different account gives it its own fairness turn.

Nothing here is product content. Do not treat the marker below as meaningful.

Refreshed for deploy: initial
Loading