bors — consistent automated testing

Automate the consolidation of git branches submitted by developers and test the merge results with your CI system (Travis CI, BuildBot, etc.) before commiting to the production master branch.

Running tests on each developer's branch is not sufficent. They may conflict in a semantic way that causes the master branch to fail when merged. Additional work that is built on such a broken master branch is tainted, unable to tell which failures are the result of an existing bug or a new one.

Instead, the combined system must be tested, as a whole, before the work becomes a part of the master branch which will form the basis of future work. Doing so, as work continues unabated, will force a backlog to be enqueued.

This system should be automated. The tool that automates this is called bors.

What happened with bors in the month of August

There's a real, official place to ask questions now. It's at forum.bors.tech. You can log in with your GitHub account, just like you log into bors itself.

We screwed up and pushd a broken pull request into production

What happened with bors in the month of July

What happened with bors in the month of June

What happened with bors in the month of May

What happened with bors in the month of April

A whirlwind tour of a build workflow