mozbase autobot status (or, "why we can't have nice things")

[Jeff Hammel]

<disclaimer:std>This email message is about $subject. If you don't care
about $subject, $ignore</disclaimer:std>

This weekend, what I would infer as either an (unsuccessful) attempt to
DOS k0s.org or to flood #ateam, both of which are easy to do by a number
of means, some idiot forced some hundred or so builds through the web
interface formerly at http://k0s.org:8010/ . While you may/may not have
known this was possible...it no longer is ;) I have removed any
functionality from http://k0s.org:8010/ that is not read-only by moving
the read-only instance that was formerly at http://k0s.org:8011/ to the
8010 port. The problem should not recur.

Likewise, per glob's request, autobot will now only notify on failed
builds. While I will miss easy notification that a build is done for
all cases, and encourage others to raise the issue if they'd rather see
this, I don't want to personally be involved in such a discussion. I
will, however, be happy to do administration and/or engineering support
work if such a decision is reached[*].

Jeff

----

[*] In general, I am happy to engineer autobot to do whatever we desire,
but I haven't heard many requests here and not having heard much about
internal CI including mozbase except "buildbot sux, switching to
jenkins" so haven't wanted to put in much time improving autobot for
this reason <disclaimer:std>This message may be repeated</disclaimer:std>

[William Lachance]

On 13-02-25 07:46 PM, Jeff Hammel wrote:
>
>
> Likewise, per glob's request, autobot will now only notify on failed
> builds. While I will miss easy notification that a build is done for
> all cases, and encourage others to raise the issue if they'd rather see
> this, I don't want to personally be involved in such a discussion. I
> will, however, be happy to do administration and/or engineering support
> work if such a decision is reached[*].

It might be annoying to receive a stream of "build success!"
notifications if there was a batch of commits all in a row, but
otherwise I think it would be reassuring to receive notification that
things are humming along nicely. It's probably not that big a deal
either way though. The important thing is to be notified when there's a
problem, and the more ways we have of communicating that the better.
Thanks for doing this!


Will