+++ This bug was initially created as a clone of Bug #644858 +++ At the moment it's taking several minutes to load, and clobbers sometimes don't take (or appear to take) on the first attempt. See Bug #644858 for the details.
Do you mean that the cron set up in bug 644858 isn't doing enough ? Perhaps there are other problems here.
I'll take this and see if I can do a little Flask app like with the graphserver app/API
Assignee: nobody → lsblakk
Priority: -- → P4
Summary: clobberer is slow to load - do routine maintenance → clobberer is slow to load - make a more optimized web interface and also a Rest API so it can be called from self-serve
I know there's been a round of improvements on clobberer, perhaps that's enough to close this - unassigning so it can be decided in triage.
Assignee: lsblakk → nobody
Component: Release Engineering → Release Engineering: Releases
QA Contact: release → bhearsum
Component: Release Engineering: Releases → Release Engineering
QA Contact: bhearsum → release
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.