✳flâneur — a map of the web's best reading

Build Runbook – Pyra

pyra.vercel.com · 95 words · saved by 1 readers

Build alerts should be handled immediately at a SEV-3 severity level. The following steps should be taken when an alert is received: Revert/rollback suspicious commits first. Fixing forward takes time and can be prone to optimism bias. The goal is to minimize resolution time and reverting is the fastest way to do that. This runbook is for build issues that don't affect Vercel end users, but if a customer could be affected, use Instant Rollback to put a known good deploymnet back in production. Use /access in Slack to request Vercel Team - Member access to be able to manually promote deployments or use Instant Rollback. Use vc bisect or the bisect functionality in the Vercel Toolbar to find the last known good deployment and to narrow down which deployment introduced the issue if it is unclear. Reach out for help! If you're not sure who to reach out to, post on the #engineering (opens in a new tab) channel. If you suspect that the issue is with the promotion process, reach out to the #

Vercel Inc - Sign In You are using an unsupported browser. For the best experience, update to a supported browser . Connecting to Sign in with your account to access Vercel Team - Vercel Your OneDrive version is not supported Upgrade now by installing the OneDrive for Business Next Generation Sync Client to login to Okta Learn how to upgrade Cookies are required Cookies are disabled on your browser. Please enable Cookies and refresh this page. Refresh Privacy Policy The page has timed out If this page does not reload automatically, please refresh your browser.

Explore this link on the map →

related reading