4 ms·
This isn't mentioned until later in the article, but it seemed important. > The worst thing about regular build failures is that they’re easy to prevent. Grayd
by jmckib 12y ago
This isn't mentioned until later in the article, but it seemed important.
> The worst thing about regular build failures is that they’re easy to prevent. Graydon Hoare literally calls keeping a clean build the “not rocket science rule”, and wrote an open source tool (bors) anyone can use to do not-rocket-science.
http://graydon2.dreamwidth.org/1597.html http://graydon2.dreamwidth.org/1597.html
- metajack 12y agoWhich has been doing amazing things for Servo and Rust for years now!
- dbaupp 12y agoA member of the Rust community, barosl, wrote Homu (bors 2.0) which Rust has been using in place of the first bors for a few months now. It's even better than the already-great first version! I'm seriously considering setting it up for my own projects, since I believe it has support for using Travis CI as a testing backend, in addition to buildbot (which Rust and Servo both use). https://github.com/barosl/homu https://github.com/barosl/homu Example interaction: https://github.com/rust-lang/rust/pull/23381#issuecomment-80858586 https://github.com/rust-lang/rust/pull/23381#issuecomment-80... Docs: http://buildbot.rust-lang.org/homu/ http://buildbot.rust-lang.org/homu/
- CyberShadow 12y agoInteresting. For the D programming language we use something similar but a little different: once a reviewer approves a pull request, they toggle an "auto-merge" flag in our CI tool, and a bot merges the pull if all tests pass (after merging with master, of course).