Closed
Bug 1083212
Opened 11 years ago
Closed 11 years ago
Requesting twig repo alder be reset
Categories
(Developer Services :: Mercurial: hg.mozilla.org, defect)
Developer Services
Mercurial: hg.mozilla.org
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Dolske, Assigned: fubar)
References
Details
(Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/278] )
I need alder reset to https://hg.mozilla.org/releases/mozilla-release/
export REPO_PATH=/releases/mozilla-release/
export TWIG=alder
cd /repo/hg/scripts/
./reset_pp_repo.sh -s /repo/hg/mozilla/$REPO_PATH -r tip -d $TWIG
| Assignee | ||
Comment 1•11 years ago
|
||
Working; should be done in about an hour.
Assignee: nobody → klibby
(In reply to Kendall Libby [:fubar] from comment #1)
> Working; should be done in about an hour.
Thanks Fubar. This looks like it is done; alder is now pointing at release. However, trying to see this in TBPL or Treeherder is difficult because we are timing out on retrieving https://hg.mozilla.org/projects/alder/json-pushes?full=1&maxhours=24 The reason that URL times out is because it is returning the data for every changeset since we switched to mercurial. I've never looked hard at what happens when we reset one of these twigs to know if that is standard or not, but I know we've never reset one to the release-branch. This issue is breaking tbpl's and treeherder's ability to display the twig's information.
Is there a smart way to get some builds triggered for this repo so that it doesn't think it needs to display all things since Hg day 0? We'd really like to have builds produced on here by end of day, but if we can't load it into our dashboards, it's going to be hard to know whether or not what we are landing is working.
CC'ing Edmorley in case he has an idea on what to try here to maybe fake out Treeherder and TBPL so they can properly displaythe repo.
Flags: needinfo?(emorley)
Comment 3•11 years ago
|
||
The pushlog DB should be empty after the script in comment 0 is run, and it seems to be according to:
https://hg.mozilla.org/projects/alder/json-pushes?startID=1
I suspect the json-pushes endpoint just doesn't handle there being zero pushes correctly (if this is the case, I'll file a bug against the pushlog) - if you make one push yourself this should self-rectify - if not, 301 :fubar :-)
Flags: needinfo?(emorley)
Updated•11 years ago
|
Whiteboard: [kanban:engops:https://kanbanize.com/ctrl_board/6/278]
Updated•11 years ago
|
Whiteboard: [kanban:engops:https://kanbanize.com/ctrl_board/6/278] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/278]
You need to log in
before you can comment on or make changes to this bug.
Description
•