-
-
Notifications
You must be signed in to change notification settings - Fork 486
deploy checklist
Shen Yang edited this page Feb 21, 2023
·
76 revisions
Note: if you click the deploy button, you have responsibility for making sure that any problems that arise are fixed!!
- If possible, work with a pair!
- Reply to the "deploy now" slack reminder to record deploy details
- DATABASE BACKUP: Take a prod heroku database backup
Look at heroku and make sure the latest qa is in staging https://dashboard.heroku.com/pipelines/ba68b367-e58a-400a-af77-5d993367c2b9- Check qa
- check each new feature and make sure they work and don't cause errors
- find possible new features here
- Check #casa-bots for bugsnag errors! Even if there is no error on the UI. Use
in:#casa-bots from:@Bugsnag
in the search box - Check in on metrics, email metrics and bugsnag, scout metrics
- Log into prod as an all casa admin and update the patch notes
- Log out
- Click the "promote" button
- Log into prod as a casa admin and double check the patch notes in the inbox
Manually verify in prod - see the logs at papertrail (login to heroku to auto-login)- Email the stakeholders from the casa@rubyforgood email saying the deploy is done + a list of stuff that changed + screenshots