Now that the last tree has been moved to the GAE cron analyzer tasks (as of <https://chromium-review.googlesource.com/c/533639/>), we can go about turning down alerts-dispatcher. Yay.

To minimize disruption, how about the following sequence of events:

* Step 0: turn off alerting for alerts-dispatcher (disable, or actually delete alert configs altogether?)

Alert config for a-d is here: https://cs.corp.google.com/piper///depot/google3/configs/monitoring/chrome_infra/task_alerts.py?q=AlertsDispatcherZeroSuccess&sq=package:piper+file://depot/google3+-file:google3/experimental&l=156

* Step 1: tell infra.cron master to stop running alerts-dispatcher's builder recipe:

Remove alerts-dispatcher config sections from
build_internal/masters/master.internal.infra.cron/master.cfg

and it's slave config from
build_internal/masters/master.internal.infra.cron/slaves.cfg

Something like this CL: https://chrome-internal-review.googlesource.com/c/394350/ ?

* Step 2: Let Infra-labs know they can de-provision slave82-c7

* Step 3: remove alerts-dispatcher related recipe code from the repo: 
https://chrome-internal.googlesource.com/chrome/tools/build_limited/scripts/slave/+/master/recipes/infra/alerts_dispatcher.py

* Step 4: Remove go/trooper playbook sections on alerts-dispatcher

* Step 5: Ain't no party like to turn-down party 'cause a turn-down party does in fact stop.
 

Now that the last tree has been moved to the GAE cron analyzer tasks (as of <https://chromium-review.googlesource.com/c/533639/>), we can go about turning down alerts-dispatcher. Yay.

To minimize disruption, how about the following sequence of events:

* Step 0: turn alerting for alerts-dispatcher (disable, or actually delete alert configs altogether?)

Alert config for a-d is here: https://cs.corp.google.com/piper///depot/google3/configs/monitoring/chrome_infra/task_alerts.py?q=AlertsDispatcherZeroSuccess&sq=package:piper+file://depot/google3+-file:google3/experimental&l=156

* Step 1: tell infra.cron master to stop running alerts-dispatcher's builder recipe:

Remove alerts-dispatcher config sections from
build_internal/masters/master.internal.infra.cron/master.cfg

and it's slave config from
build_internal/masters/master.internal.infra.cron/slaves.cfg

Something like this CL: https://chrome-internal-review.googlesource.com/c/394350/ ?

* Step 2: Let Infra-labs know they can de-provision slave82-c7 (prod) and slave26-c7 (staging)

* Step 3: remove alerts-dispatcher related recipe code from the repo: 
https://chrome-internal.googlesource.com/chrome/tools/build_limited/scripts/slave/+/master/recipes/infra/alerts_dispatcher.py

* Step 4: Remove go/trooper playbook sections on alerts-dispatcher

* Step 5: Remove alerts-dispatcher from viceroy dashboards.

* Step 6: Ain't no party like to turn-down party 'cause a turn-down party does in fact stop.