🤖 👀 🤖

Summary

This is a simple bot that watches LLVM's upstream buildbots @ http://lab.llvm.org/buildbot/#/console , and posts updates to two discord channels.

In order to use this bot, a discord server must exist and have the following two channels:

• #buildbot-status
• #buildbot-updates

The bot assumes that no one posts in these channels but it. If someone-who-isn't-this-bot does post in either of these channels, their messages may be deleted by the bot at some point in the future.

#buildbot-status is a channel that summarizes the state of all upstream bots. #buildbot-updates gets a new message whenever one or more bots are found to be newly-broken.

If you want this bot in your discord server, feel free to ping me and I'll send along an invite link.

Contributing

The bot isn't particularly configurable/general, since it doesn't seem hugely applicable outside of users of LLVM's buildbot version (0.8.5).

Contributions are welcome nonetheless. Though this bot isn't officially sponsored/supported by LLVM in any way (e.g., it's a hobby project), I ask that you observe LLVM's code of conduct while you're here. :)

Running the bot

The way that is both new and shiny

Running docker build -t llvm_buildbot_monitor . in this directory will produce a docker image that gets you the majority of the way there.

The only thing missing is credentials and database info, which are both specified during docker run. My docker run command looks something like:

docker run \
  --rm \
  --env DISCORD_TOKEN="${MY_DISCORD_TOKEN}" \
  -v "${PATH_TO_DIR_CONTAINING_DB_FILE}:/db"
  -v "${HOME}/llvmbb_logs:/logs"
  --it \
  llvm_buildbot_monitor

Notes:

• The default db file is called db.sqlite3. I store it in db/ within this repo (though it's gitignore'd).
• The /logs volume is optional. If it's specified, the default container output will be minimal, instead being redirected to log files. If not specified, output will go to stdout/stderr.

The old way

DISCORD_TOKEN=foo ./run.py is what I used to run the bot on my server. It's sorta awkward to hold, since that script is part of this repo, yet it syncs the bot to somewhere under ~/llvmbb_monitor/.

...In any case, that script takes care of polling github for new updates, and automatically building/testing any new commits that fly in. If all of the tests pass, it'll launch the new version of the bot.