Open Bug 1017724 (try-tracker) Opened 10 years ago Updated 7 years ago

[tracker] issues with try

Categories

(Developer Services :: Mercurial: hg.mozilla.org, defect)

defect
Not set
normal

Tracking

(Not tracked)

People

(Reporter: hwine, Unassigned)

References

Details

(Keywords: meta, Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/756] )

There are a number of bugs all related to try. This will be a tracker.
Depends on: 994028
Depends on: 925354
Depends on: 691459
Depends on: 770811
Depends on: 988665
Depends on: 1001735
Alias: try-tracker
Depends on: 1035660
Could (/should) we combine this with bug 770811 - or is there a difference? :-)
Flags: needinfo?(hwine)
I see the difference that bug 770811 evolved into primarily being about pushlog issues (databases), while this bug is about mercurial issues (tag caches, monitoring)

I'll update the summary of bug 770811 to reflect that -- while they have similar symptoms to users, they are very different code paths.
Depends on: 1045089, 992368
Flags: needinfo?(hwine)
Depends on: 1048886
Depends on: 1040308, 851398, 1036122
We could likely reduce load on hg.m.o if we reliably published hg pushes to pulse, and our tools consumed that rather than hammering on /json-pushes - bug 1022701.
Depends on: 1022701
Depends on: 1050006
Depends on: 1049530
No longer depends on: 1022701
Depends on: 1050377
Component: WebOps: Source Control → Mercurial: hg.mozilla.org
Product: Infrastructure & Operations → Developer Services
Whiteboard: [kanban:engops:https://kanbanize.com/ctrl_board/6/107]
Whiteboard: [kanban:engops:https://kanbanize.com/ctrl_board/6/107] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/756] [kanban:engops:https://kanbanize.com/ctrl_board/6/107]
Whiteboard: [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/756] [kanban:engops:https://kanbanize.com/ctrl_board/6/107] → [kanban:engops:https://mozilla.kanbanize.com/ctrl_board/6/756]
Assignee: server-ops-webops → nobody
QA Contact: nmaul → hwine
QA Contact: hwine → klibby
You need to log in before you can comment on or make changes to this bug.