Closed
Bug 790707
Opened 13 years ago
Closed 13 years ago
Socorro code push for mobeta release at 5:00pm pacific 9/12/2012
Categories
(Infrastructure & Operations Graveyard :: WebOps: Other, task)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: mpressman, Assigned: jd)
References
Details
(Whiteboard: [mobeta][push interrupt])
Attachments
(1 file)
10.70 KB,
text/plain
|
Details |
We need to push the latest socorro code during a downtime
Updated•13 years ago
|
Assignee: server-ops → server-ops-webops
Component: Server Operations → Server Operations: Web Operations
QA Contact: jdow → cshields
Summary: Socorro code push for mobeta release at 5:00pm pacific 9/121/2012 → Socorro code push for mobeta release at 5:00pm pacific 9/12/2012
Comment 2•13 years ago
|
||
We must complete bug 790705 before starting this bug.
The build to push:
https://ci.mozilla.org/job/socorro-release/227/artifact/socorro.tar.gz
The steps to take (note DB failover (bug 790711), upgrades, changes to cron jobs, and puppet):
https://wiki.mozilla.org/Socorro:Releases/18
Assignee | ||
Updated•13 years ago
|
Assignee: server-ops-webops → jcrowe
Assignee | ||
Updated•13 years ago
|
Whiteboard: [mobeta] → [mobeta][push interrupt]
Assignee | ||
Comment 3•13 years ago
|
||
Push complete.
Assignee | ||
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 4•13 years ago
|
||
QA is complete -- bumping to verified: thank you all for a smooth release!
* manual bfts and smoke tests pass
* automation passes (http://qa-selenium.mv.mozilla.com:8080/job/socorro.prod/4505/)
* new feature and defects for milestone 18 have been re-verifed (https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced;target_milestone=18;product=Socorro;list_id=4368740)
Status: RESOLVED → VERIFIED
Updated•11 years ago
|
Component: Server Operations: Web Operations → WebOps: Other
Product: mozilla.org → Infrastructure & Operations
Updated•6 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
•