Instead of depth=1, try depth=5. This way, if something gets landed
before travis had a chance to build, it'll still get tested, at least
post-facto.
This is the root cause of the build failure at
https://travis-ci.org/rapid7/metasploit-framework/builds/11436293
That commit is not available because the HEAD pointer moved past it with
the next commit; IOW, we landed too quick for Travis to rspec each
change, which is generating failed build messages.
If there was really a failure in there, it'd be a pain now to determine
which commit actually broke the build.
Add the .travis.yml so that travis-ci.org knows which rubies (1.8.7 and
1.9.3 to run rake against. Add the build status button to the README.md
so that people can see if the specs are passing from the main
rapid7/metasploit-framework page on github just like other open source
projects.
Tod Beardsley
Luke Imhoff
James Lee