|
|
| Line 1: |
Line 1: |
| == Push to production ==
| | |
| # Ensure that the expected build is listed on https://wiki.mozilla.org/Socorro:Releases and https://crash-stats.allizom.org/status
| |
| # Release Manager: Esnure we have [[Socorro/Release_Procedure/Checklists/VerifyQA | QA sign off]] and note on https://wiki.mozilla.org/Socorro:Releases
| |
| # File a push bug in Socorro/Infra, for example see: {{bug|735837}}
| |
| # Coordinate with IT to run [[Socorro/Release_Procedure/Checklists/DatabaseChange | Database changes]]
| |
| # Ask QA to run test bots.
| |
| # Socorro devs verify logs on each server: `/var/log/socorro/*.log`, `/var/log/socorro/kohana/*.php`
| |
| # Devs also verify from StatsD, Ganglia, and Status Page (links?)
| |
| # If cron changes exist, schedule verification of cron job changes for after their next scheduled run
| |
| # Update https://wiki.mozilla.org/Socorro:Releases with push bug link
| |
| # Tagged release and push changes to github. Sample commands below:
| |
| #:<pre>git tag 50</pre>
| |
| #:<pre>git push mozilla 50</pre>
| |
| # Update https://github.com/mozilla/socorro/releases/ with release tag link to github
| |
| # Finally, send email to socorro-dev and tools-socorro lists announcing the release
| |