Commit Graph

60 Commits (22df7c00716f27dc48e8fd3951b8eabb48dc65a3)

Author SHA1 Message Date
Tod Beardsley 5ae4215229
Hey Travis what's up with your rake version? 2014-01-06 12:11:07 -06:00
Tod Beardsley 7eb4e10999 Extend Travis's depth a bit
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.
2013-09-16 17:23:16 -05:00
Luke Imhoff 0f6b05321e Configure travis-ci to use database for rake spec
[#46224565]
2013-03-15 08:48:20 -05:00
James Lee 040296f13a Make travis install libpcap-dev 2013-02-19 15:41:31 -06:00
James Lee 16390e31c6 Attempt to make travis useful again
Lowers the history depth from the default of 100.
2013-01-24 15:48:04 -06:00
James Lee de85ac5caf STFU, travis 2013-01-10 13:53:47 -06:00
James Lee 0a47586ece Last commit should make 1.8.7 specs pass 2012-11-20 19:45:28 -06:00
James Lee b8e3bfe1da Add IRC notifications and allow 1.8.7 to fail
This should tell travis to run the tests against 1.8.7 but not to
consider the whole build broken if it fails (which it currently does)
2012-11-09 15:02:09 -06:00
James Lee 3df9dfcea2 Disable CI testing on 1.8.7 for now
To stop the flood of everything-is-broken emails
2012-11-07 20:53:55 -06:00
Luke Imhoff 726cf8bb94 travis-ci.org integration
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.
2012-11-07 08:29:44 -06:00