Closed
Bug 1098521
Opened 10 years ago
Closed 6 years ago
make deployment process easier, more robust
Categories
(MozReview Graveyard :: General, defect, P3)
MozReview Graveyard
General
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: fubar, Assigned: fubar)
Details
current deploy process is less than ideal, using webops' deploy stuff. also, it doesn't handle v-c-t. it should also drain/undrain the web heads for restarting httpd, similar to what BMO does. :gps likely has other, probably better, ideas.
Comment 1•10 years ago
|
||
Something we also should probably consider when deploying is blocking pushes to the review repos and letting in progress pushes complete. The part of the system talking to Review Board during the push makes many requests - if Review Board goes down mid push it will be left in a partial state. The user *should* be able to discard the broken state, or just push overtop of it, but I'm not 100% sure that will cover all possible cases. We should at least investigate this.
Comment 2•10 years ago
|
||
We can easily have a hook on the Mercurial server that looks for the presence (or lack thereof) of a heartbeat file and deny all push actions until the check passes.
Comment 3•9 years ago
|
||
You did work on this recently, right? What did you do, and what else should we do?
Flags: needinfo?(gps)
Comment 4•9 years ago
|
||
No, we still need to invest in this. This overlaps strongly with work inside v-c-t for configuring the testing environment. I'll find time to talk to fubar sometime about making this all suck less.
Flags: needinfo?(gps)
Updated•9 years ago
|
Priority: -- → P1
Updated•8 years ago
|
Product: Developer Services → MozReview
Updated•8 years ago
|
Priority: P1 → P3
Comment 5•6 years ago
|
||
MozReview is now obsolete. Please use Phabricator instead. Closing this bug.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•