Socorro/Release Process: Difference between revisions
< Socorro
Jump to navigation
Jump to search
(formatting) |
(note about jenkins) |
||
| Line 6: | Line 6: | ||
* code is branched per https://wiki.mozilla.org/Socorro/Release_Branch_Strategy | * code is branched per https://wiki.mozilla.org/Socorro/Release_Branch_Strategy | ||
* staging data is refreshed and new build is loaded to branch staging server (crash-stats.allizom.org) | * staging data is refreshed and new build is loaded to branch staging server (crash-stats.allizom.org) | ||
** builds are created by the Jenkins instance at https://jenkins.mozilla.org/job/socorro/ | |||
** the same build is pushed to staging and (once QA has approved) production, for example https://jenkins.mozilla.org/job/socorro/519/artifact/branch/socorro.tar.gz | |||
== Verification == | == Verification == | ||
Revision as of 20:01, 30 June 2011
New feature/bugfix
- Socorro bugs are triaged and "Target Milestone" field in bugzilla is set
- As bugs are resolved, QA verifies them against the trunk staging server (crash-stats-dev.allizom.org)
Code freeze
- code is branched per https://wiki.mozilla.org/Socorro/Release_Branch_Strategy
- staging data is refreshed and new build is loaded to branch staging server (crash-stats.allizom.org)
- builds are created by the Jenkins instance at https://jenkins.mozilla.org/job/socorro/
- the same build is pushed to staging and (once QA has approved) production, for example https://jenkins.mozilla.org/job/socorro/519/artifact/branch/socorro.tar.gz
Verification
- QA verifies fixes against branch staging server
- Socorro devs verify logs on each server:
- /var/log/socorro/*.log
- /var/log/socorro/kohana/*.php
Push to production
- When QA signs off, a push bug in mozilla.org/Server Ops
- for example see: bug 667819
- Socorro devs verify logs on each server:
- /var/log/socorro/*.log
- /var/log/socorro/kohana/*.php