-
-
Notifications
You must be signed in to change notification settings - Fork 484
deploy checklist
Shen Yang edited this page Dec 17, 2022
·
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/ab5437b7-b7da-4204-bcfc-33bac4466347
- Check staging
- as Volunteer, log in, create case contact, follow up on case contact
- as Supervisor, check that a volunteer has cases and those cases have case contacts
- as Admin, Check reimbursement and export. If there are changes to imports, test the imports.
- Check #casa-bots for errors from staging! 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
- Click the "promote" button
- 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
- Update the meeting planning doc https://docs.google.com/document/d/1eUv8XoiOljDLK951MgKXNs1Zr5hs_1K41qZHgw5RY8o/edit#heading=h.9np08bylf0hn
- Post to slack that you are DONE!