Closed
Bug 777521
Opened 12 years ago
Closed 12 years ago
reset try repo
Categories
(Developer Services :: General, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: hwine, Assigned: cshields)
References
Details
(Whiteboard: [tegras])
Per discussions, reset try repo during the tree closure for this weekend's down time.
Comment 1•12 years ago
|
||
Pushing to normal so it doesn't page oncall before the downtime. What's the exact date/time of this downtime window?
Severity: major → normal
Comment 2•12 years ago
|
||
Sunday July 29 from 1200-1500 PDT (1900-2200 UTC).
Comment 3•12 years ago
|
||
(In reply to Ravi Pina [:ravi] from comment #2)
> Sunday July 29 from 1200-1500 PDT (1900-2200 UTC).
Thanks. I will be on a plane, so this will probably need someone else to help reset. Not sure if bkero is back from blackhat by then.
Comment 4•12 years ago
|
||
(In reply to Shyam Mani [:fox2mike] from comment #3)
> (In reply to Ravi Pina [:ravi] from comment #2)
> > Sunday July 29 from 1200-1500 PDT (1900-2200 UTC).
>
> Thanks. I will be on a plane, so this will probably need someone else to
> help reset. Not sure if bkero is back from blackhat by then.
Who can reset of try repo in this downtime?
Flags: needs-treeclosure?
Comment 5•12 years ago
|
||
Steps :
1) Login to hgssh1.dmz.scl3.mozilla.com as root
2) Run /repo/hg/scripts/reset_try.sh in a screen session
3) Profit
Note : the script will preserve the current try repo.
Comment 6•12 years ago
|
||
4) Give RelEng a prod to reset the scheduler masters
5) Share profit :-)
Comment 7•12 years ago
|
||
Also, this is to go ahead provided Corey and John sign off on it. We have an upstream hg bug tracking the current issues with try and we might want to preserve state to find a solution.
Comment 8•12 years ago
|
||
(Switching blocking bugs, since I think bug 770811 was the intended target here)
Assignee | ||
Comment 9•12 years ago
|
||
try was reset this morning, see 778062
Assignee | ||
Updated•12 years ago
|
Assignee: server-ops-devservices → cshields
Updated•10 years ago
|
Component: Server Operations: Developer Services → General
Product: mozilla.org → Developer Services
You need to log in
before you can comment on or make changes to this bug.
Description
•