Closed
Bug 1618818
Opened 5 years ago
Closed 5 years ago
Extract the existing reporter bot logic separately into a reporter tool
Categories
(Tree Management :: Perfherder, task, P1)
Tree Management
Perfherder
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: igoldan, Assigned: onegru)
References
Details
Attachments
(1 file)
The current logic we need to extract resides on these SLOCs.
An independent class for it is ideal.
|
Reporter | |
Comment 1•5 years ago
|
||
Octavian, I'm assigning you to this bug.
|
|
Reporter | |
Updated•5 years ago
|
Assignee: nobody → onegru
|
||
Comment 2•5 years ago
|
||
|
|
Reporter | |
Updated•5 years ago
|
Priority: P2 → P1
|
|
Reporter | |
Comment 3•5 years ago
|
||
I just realized that this ticket is redundant. The convenient reporter bot I envisioned was already implemented by the BackfillReportMaintainer.
What distracted me was the verbose instantiation of the AletsPicker & IdentifyAlertRetriggerables classes. But they're acceptable for the time being.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•