Push Duty (Next)¶
Push duty rotates each week to another developer. The current rotation is:
eviljeff
mat
kmeinhardt
Check out the Add-ons calendar for a list of events.
Before the push¶
Before a push, we continuously land and deploy code to dev by merging PRs to master in respective repositories. During this time, individuals and/or the push hero might update the upcoming release document with notes for pre/post deployment tasks. Refer to the release docs for more information.
On Tuesday at 09:00 PT, we deploy to stage. This is the time to:
push tags for manually deployed services (see tag services)
publish the release document. (see release docs)
QA and cherry pick if necessary (see staging QA and cherry picking)
During Push¶
On Thursday at 09:00 PT, we deploy to production. This is the time to:
meet with SRE and QA in the remora slack channel (see remora)
approve the stage deployments to push to production (see deployments)
push extension-workshop to production if needed (see tag-services)
monitor the push in sentry and grafana for any issues (see monitoring)
After the push¶
create a new release document for the next push hero (see release docs)
update the topic of the AMO Matrix channel and the #remora slack channel to include the handle of next week’s push hero (see :doc:
remora <./remora>)
Runbooks¶
This section will outline the steps to take for specific actions that you might need to perform before, during and/or after a push. The push runbook is a living document and should be updated as needed. Please reference it in the push notes for each push. As well as in the above push duty document.