Socorro/Release Process: Difference between revisions
(note about jenkins) |
|||
| Line 21: | Line 21: | ||
** /var/log/socorro/*.log | ** /var/log/socorro/*.log | ||
** /var/log/socorro/kohana/*.php | ** /var/log/socorro/kohana/*.php | ||
== PostgreSQL Database Changes == | |||
Cumulative schema changes are stored in the various directories under /scripts/upgrades in the source code. Each directory is tied to a Socorro version (e.g. /scripts/upgrades/2.1/), and contains scripts to upgrade from the prior release version to the current version. | |||
For most database changes, there will be a shell script upgrade.sh. This shell script will contain calls to one or more python scripts and/or SQL files contained in the same directory and will execute them in order. In some cases, there will be a different script for the development server, in which case there will be an upgrade-dev.sh script to be executed on development and stage. | |||
Some SQL database changes require downtime or require large amounts of time to execute, or may require downtimes. These will be scheduled and executed in advance of the code upgrade. Their scripts will be present in upgrade.sh for reference, but commented out. | |||
stageDB and production autosync the Socorro SVN repository trunk automatically every hour. As such, scripts should be available to execute on each database server in /data/socorro/applications/scripts/upgrades/ | |||
Revision as of 18:35, 18 July 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
PostgreSQL Database Changes
Cumulative schema changes are stored in the various directories under /scripts/upgrades in the source code. Each directory is tied to a Socorro version (e.g. /scripts/upgrades/2.1/), and contains scripts to upgrade from the prior release version to the current version.
For most database changes, there will be a shell script upgrade.sh. This shell script will contain calls to one or more python scripts and/or SQL files contained in the same directory and will execute them in order. In some cases, there will be a different script for the development server, in which case there will be an upgrade-dev.sh script to be executed on development and stage.
Some SQL database changes require downtime or require large amounts of time to execute, or may require downtimes. These will be scheduled and executed in advance of the code upgrade. Their scripts will be present in upgrade.sh for reference, but commented out.
stageDB and production autosync the Socorro SVN repository trunk automatically every hour. As such, scripts should be available to execute on each database server in /data/socorro/applications/scripts/upgrades/