Closed
Bug 483999
Opened 15 years ago
Closed 15 years ago
Push SUMO 0.9.5 to production on Tuesday March 24th
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: laura, Assigned: dmoore)
Details
(Whiteboard: Push @ 03/24/2009)
Details to come, this is just the heads up.
Reporter | ||
Comment 1•15 years ago
|
||
Renaming release for marketing purposes.
Summary: Push SUMO 1.0 to production on Tuesday March 24th → Push SUMO 0.9.5 to production on Tuesday March 24th
Updated•15 years ago
|
Whiteboard: Push @ 03/24/2009
Reporter | ||
Comment 2•15 years ago
|
||
Tag is http://svn.mozilla.org/projects/sumo/tags/0.9/0.9.5_20090324_r23716/ SQL changes are required, and will follow in this bug
Reporter | ||
Comment 3•15 years ago
|
||
You'll also need to run sudo htaccess.sh for this release as per https://bugzilla.mozilla.org/show_bug.cgi?id=479848
Updated•15 years ago
|
Assignee: server-ops → dmoore
Reporter | ||
Comment 4•15 years ago
|
||
SQL to be run. Please run SQL before doing the svn switch. https://bug480458.bugzilla.mozilla.org/attachment.cgi?id=364507&t=6b5bGB9Q76 https://bug481316.bugzilla.mozilla.org/attachment.cgi?id=367514 (this one might take a while) https://bug481303.bugzilla.mozilla.org/attachment.cgi?id=366205
Reporter | ||
Comment 5•15 years ago
|
||
A couple extra notes on the push. I have been told by IT that the checkout on prod is set up slightly differently from stage. Be aware that inside the tag the webroot/ directory is the part that needs to be the document root on apache. I am not sure if the scripts/ directory is checked out at present but it will be needed after this release, so it would be a good time to check. The procedure should be as follows: 1. Update the database as per the above SQL. The second query is an ALTER TABLE and may take some time to execute. 2. svn switch to the new tag. 3. Change into the webroot directory and run sudo htaccess.sh This updates all of the various htaccess files throughout the directory hierarchy. 4. After all this is complete, you will need to purge the various caches associated with SUMO so that the push can be verified. There are three caches that need purging. They need to be purged in the following order: 4.1 Smarty template cache. In webroot/templates_c, rm *.tpl and rm *.tpl.php In webroot/temp/cache, rm everything *except for* index.php 4.2 Memcache We do whole page caching in memcache. The memcache servers we use can be found listed in webroot/db/local.php 4.3 Netscaler That should be it! Thanks and good luck.
Assignee | ||
Comment 6•15 years ago
|
||
Pushed as requested.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Comment 7•15 years ago
|
||
Verified FIXED; checked several bugs like bug 482212, bug 482474, and bug 474895, among a few others.
Status: RESOLVED → VERIFIED
Updated•11 years ago
|
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Updated•5 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•