Perfherder alerts planning

[William Lachance]

[ Bcc'ing a few folks who might be interested, please send followups to
the Treeherder mailing list ]

Hey all,

Thought I'd inaugurate the Treeherder mailing list
(https://groups.google.com/d/msg/mozilla.tools.treeherder/lRFIdzXiNzU/N3tmJWZsBwAJ)
with a post about my short-term plan for Perfherder alerts. As some
people are aware, my goal for this quarter is to get a basic performance
sheriffing view up and running:

https://docs.google.com/document/d/1bPJyyvepbkz3suPdEg_ikOi1nQiCcaygjb4iw6OUGjI/edit?usp=sharing

As of this week, we now have a very basic "alerts" view working on stage:

https://treeherder.allizom.org/perf.html#/alerts

This currently requires using a console command to generate the content
and is read-only. This isn't really that useful, so I'm going to be
working on the following items:

* Generate performance alerts on ingestion
(https://bugzilla.mozilla.org/show_bug.cgi?id=1228154). Note that I'm
doing this in a somewhat sub-optimal way to get a prototype done
sooner... fortunately it should be easy to change once we have the
necessary backend support. See the bug for more details.
* Add support for reassigning an alert to a new summary
(https://bugzilla.mozilla.org/show_bug.cgi?id=1228156)
* Add support for setting alert status and linking to a bugzilla bug
(https://bugzilla.mozilla.org/show_bug.cgi?id=1228158)

I expect to work on these items roughly in order. If you have any
comments or questions, please let me know either here or in the bugs. My
goal is to have something viable working on Treeherder staging by the
Mozilla all hands in Orlando.

Will

[William Lachance]