WARNING: This project is under heavy construction.
Bot.io is a fully scriptable build/test bot for Github projects. It is similar to Travis-CI in purpose, but most of the action happens at the pull request level and there are no constraints on what types of tests you can run. (Also you have to provision your own test/build servers).
Bot.io is written in Node.js and works on both Windows and Unix. Its previous incarnation has been battle-tested at Mozilla's pdf.js project since late 2011.
- Reviewers write shell-like scripts such as on_cmd_test.js that tell the bot what to do when it receives a command. (Any arbitrary command can be defined).
- The bot listens for comments like
/botio testin pull requests, and runs the corresponding script when a command is detected.
- The bot reports back to the pull request with a comment containing the test result.
Live browser tests: Bot.io comes with a built-in web server, so if your project is a web app you can create a script, say on_cmd_publish.js, to deploy select files into the server. Reviewers can then issue
/botio publishand take the PR for a spin in their browser before merging it.
Post-receive scripts: Bot.io scripts can do just about anything shell scripts can do, and they can hook into other Github events. For example, the script on_push.js is executed every time new commits are pushed to the master branch.
Bot.io depends on Node.js and
git. To get started, create a new directory for your Botio files. In this directory, bootstrap Github hooks/configuration files, and start the server (replace
--user arturadib and
--repo arturadib/pdf.js by your corresponding user and repo names, and set
--port to the desired port number for the Botio server):
$ npm install -g botio $ mkdir botio-files; cd botio-files $ botio bootstrap --repo arturadib/pdf.js --user arturadib --pwd password123 --port 8877 $ botio start --user arturadib --pwd password123
You can now trigger your first Bot.io job by leaving the following comment on any pull request in your repo:
The bot should write back a hello world response in the PR discussion. At this point you will probably want to customize your bot scripts, like
When Github sends a new notification, Botio automatially fires up the corresponding script. For example,
push notifications will trigger
on_push.js, whereas a comment like
/botio publish (by a whitelisted user) will trigger
If you want the bot to leave comments as a different user (here are some gravatar suggestions), simply start the server with the desired user credentials:
$ botio start --user fancy_pants_bot --pwd password123
Here are some important properties you might want to modify:
name: Name of the bot, in case you have multiple ones (e.g.
whitelist: Array of Github user names allowed to trigger Botio commands via pull request comments
public_dir: Path to the base directory where all web-facing files should be stored
private_dir: Path to the base directory where all tests will be run
script_timeout: (In seconds) Will kill any script that takes longer than this
On your Github repo, go to Admin > Service Hooks > Post-Receive URLs and disable the URL corresponding to the IP of your machine. (Don't forget to save it).
At the moment Bot.io uses a simple queueing system, so only one test can be run at a time. This might change in the future.
Bot.io only responds to white-listed users.