Commit Graph

70 Commits (ca0314053181172b3a8b89bd6543738b400cbda2)

Author SHA1 Message Date
darkbushido 715f54b755
trying to get travis-ci to run cucumber 2014-08-20 19:43:13 -05:00
Tod Beardsley 2d0ff4b9fb
Travis shouldn't autofail msftidy fails... yet
[SeeRM #8498]
2014-04-08 14:05:42 -05:00
Tod Beardsley 4ce2203355
Can we test the modules before the bundle install? 2014-04-03 10:41:42 -05:00
Tod Beardsley 3c657e1f0a
Okay just run it once 2014-04-03 10:25:55 -05:00
Tod Beardsley 2a26b7e9b9
Let's not screw up the .travis.yml 2014-04-03 10:00:19 -05:00
Tod Beardsley 868a7f6b4c
Add a new .travis.yml 2014-04-02 11:23:43 -05:00
Tod Beardsley bd5e327442
Also remove SPOTCHECK_RECENT from travis. 2014-04-02 11:12:54 -05:00
Tod Beardsley 87412be33d
Squash commit Travis-able msftidy checks
This change updates msftidy to be run automatically for new modules
added since the last tag release because we can't rely on folks using
tools/dev/pre-commit-hook before submitting a PR. Now, when one attempts
to open a PR with a non-tidy'ed module, the build will fail out of the
gate.

Related to the 100s of msftidy errors extant today.

[SeeRM #8498]

commit c894e52de5705a1133191be5e9caf3ebdee33621
Author: Tod Beardsley <tod_beardsley@rapid7.com>
Date:   Fri Jan 31 14:17:02 2014 -0600

    Add a jacked up title to test travis. Revert this!

commit 2f00c190be71aeb456a7a546071286fd6d670bc1
Author: Tod Beardsley <tod_beardsley@rapid7.com>
Date:   Fri Jan 31 11:39:42 2014 -0600

    Allow for checking and spotchecking.

commit db11e8dfad5381030b08c431a183dbafe7a5f304
Author: Tod Beardsley <tod_beardsley@rapid7.com>
Date:   Thu Jan 30 17:16:37 2014 -0600

    Whoops, need to exit an Integer always.

commit 12d131d3157a78ff11e597476138323ed0a062fc
Author: Tod Beardsley <tod_beardsley@rapid7.com>
Date:   Thu Jan 30 16:59:35 2014 -0600

    Allow for exit statuses from msftidy.

commit 2c3b294ff17416f49935472caf2b6be3dbdd93a4
Author: Tod Beardsley <tod_beardsley@rapid7.com>
Date:   Thu Jan 30 15:36:43 2014 -0600

    Be more dynamic about tag checking years

commit d5d8a0b05ac17fb18666a9c252dbb6928d6b5e56
Author: Tod Beardsley <tod_beardsley@rapid7.com>
Date:   Thu Jan 30 14:36:44 2014 -0600

    Don't warn when there's really nothing

commit fb44a3142fb01eb2647c1c240bb1cc2e7bf59120
Author: Tod Beardsley <tod_beardsley@rapid7.com>
Date:   Thu Jan 30 14:21:50 2014 -0600

    Revert the intentional failure

    This reverts commit 99a7630b0da301b27ac495cb027009a8cd9e2caf.

    Fun fact: Reverting a commit does not automatically sign with my current
    aliases, one must git revert then git c --amend.

commit 99a7630b0da301b27ac495cb027009a8cd9e2caf
Author: Tod Beardsley <tod_beardsley@rapid7.com>
Date:   Thu Jan 30 14:08:05 2014 -0600

    Cause an exit status in precommit check

    Maybe travis will see these and fail the build.

    Don't forget to revert this commit @todb-r7 !

commit 5a3b2fcd9598fae51a0dd2c7c87680c703a85448
Author: Tod Beardsley <tod_beardsley@rapid7.com>
Date:   Thu Jan 30 13:11:04 2014 -0600

    Update msftidy pre-commit-hook for spotchecking

commit 3f255e36dad9ed3081aaf359f845525d96872ef0
Author: Tod Beardsley <tod_beardsley@rapid7.com>
Date:   Thu Jan 30 12:35:16 2014 -0600

    Travis should run msftidy via precommit hook

commit 0959d9d2d281590a94c0ac960e43b74354e4e21b
Author: Tod Beardsley <tod_beardsley@rapid7.com>
Date:   Thu Jan 30 12:25:53 2014 -0600

    Add SPOTCHECK_RECENT to msftidy.rb
2014-01-31 14:19:04 -06:00
Tod Beardsley 5c77f4dc0f
Don't try to bundle exec before bundle install 2014-01-06 12:47:36 -06:00
Tod Beardsley e168b92b0c
Add bundle exec rake to avoid system rake 2014-01-06 12:29:50 -06:00
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