please consider adding a "push it to the top of the hill and try again" button to /builders

[LaMont Jones]

Right now, when a buildd becomes disabled because of (for example) "no route to host" (which is an indication of a timing issue somewhere that we should look into...), it takes many button presses to tell launchpad that "it's all OK now, put the builder back"

In instances where several buildds go away (firewall reboots come to mind), this can be cumbersome.

Disabled builders should (for buildd-admins) provide more info that just 'Disabled' - please add the reason to the main /builders page. Also, please consider a buildd-admin available button there that will put a Disabled builder back to OK status in one press, instead of four.

[Julian Edwards (julian-edwards)]

We can probably make the /builders page a bit more ajaxy and set more of the builder properties inline.