metasploit-framework/.travis.yml

env:
  - RAKE_TASK=cucumber
  - RAKE_TASK=cucumber:boot
  - RAKE_TASK=spec SPEC_OPTS="--tag content"
  - RAKE_TASK=spec SPEC_OPTS="--tag ~content"

language: ruby
matrix:
  fast_finish: true
before_install:
  - rake --version
  - sudo apt-get update -qq
  - sudo apt-get install -qq libpcap-dev
  # Uncomment when we have fewer shipping msftidy warnings.
  # Merge committers will still be checking, just not autofailing.
  # See https://dev.metasploit.com/redmine/issues/8498
  # - ln -sf ../../tools/dev/pre-commit-hook.rb ./.git/hooks/post-merge
  # - ls -la ./.git/hooks
  # - ./.git/hooks/post-merge
before_script:
  - cp config/database.yml.travis config/database.yml
  - bundle exec rake --version
  - bundle exec rake db:create
  - bundle exec rake db:migrate
script:
  # fail build if db/schema.rb update is not committed
  - git diff --exit-code && bundle exec rake $RAKE_TASK

rvm:
  - '1.9.3'
  - '2.1'

notifications:
  irc: "irc.freenode.org#msfnotify"

git:
  depth: 5
Add cucumber to test matrix MSP-11153 2014-08-27 21:50:25 +00:00			`env:`
			`- RAKE_TASK=cucumber`
updating how we use cucumber to match lukes changes 2014-09-02 23:57:55 +00:00			`- RAKE_TASK=cucumber:boot`
SPEC -> SPEC_OPTS MSP-11145 Fix typo in .travis.yml 2014-10-27 19:46:40 +00:00			`- RAKE_TASK=spec SPEC_OPTS="--tag content"`
			`- RAKE_TASK=spec SPEC_OPTS="--tag ~content"`
fixing a merge error with travis.yml 2014-09-03 00:07:39 +00:00
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 14:29:44 +00:00			`language: ruby`
Enable fast_finish on travis-ci MSP-11616 If any one build fails the entire build will be marked as failed so the github status can be written back faster. 2014-11-17 14:33:05 +00:00			`matrix:`
			`fast_finish: true`
Make travis install libpcap-dev 2013-02-19 21:41:31 +00:00			`before_install:`
Don't try to bundle exec before bundle install 2014-01-06 18:47:36 +00:00			`- rake --version`
Make travis install libpcap-dev 2013-02-19 21:41:31 +00:00			`- sudo apt-get update -qq`
			`- sudo apt-get install -qq libpcap-dev`
Travis shouldn't autofail msftidy fails... yet [SeeRM #8498] 2014-04-08 19:05:17 +00:00			`# Uncomment when we have fewer shipping msftidy warnings.`
			`# Merge committers will still be checking, just not autofailing.`
			`# See https://dev.metasploit.com/redmine/issues/8498`
			`# - ln -sf ../../tools/dev/pre-commit-hook.rb ./.git/hooks/post-merge`
			`# - ls -la ./.git/hooks`
			`# - ./.git/hooks/post-merge`
Can we test the modules before the bundle install? 2014-04-03 15:41:42 +00:00			`before_script:`
Configure travis-ci to use database for rake spec [#46224565] 2013-03-15 13:48:20 +00:00			`- cp config/database.yml.travis config/database.yml`
Add bundle exec rake to avoid system rake 2014-01-06 18:29:50 +00:00			`- bundle exec rake --version`
			`- bundle exec rake db:create`
			`- bundle exec rake db:migrate`
Move git diff --exit-code so build fails instead of errors MSP-11616 With `git diff --exit-code` in `before_script` it caused the build to show as errored in travis and didn't turn the merge button red, so try moving to the `script` section to see if that will make the merge button red. 2014-11-14 18:50:27 +00:00			`script:`
Fail travis build if db/schema.rb is missing commit of update MSP-11616 Use `git diff --exit-code` to exit with 1 and fail the build if there is an update to db/schema.rb after `rake db:migrate` runs on travis. 2014-11-14 15:57:03 +00:00			`# fail build if db/schema.rb update is not committed`
Don't run `bundle exec rake $RAKE_TASK` if `git diff --exit-code` with 1 MSP-11616 Travis runs all entries in the script section even if earlier entries exit with 1 and only fails the build as a whole once all entries have run by &&ing together the exit codes. Running `bundle exec rake $RAKE_TASK` if the db/schema.rb is missing updates is unnecessary, so use `&&` in the script section to stop `bundle exec rake $RAKE_TASK` from running if `git diff --exit-code` exits with 1. 2014-11-17 14:12:47 +00:00			`- git diff --exit-code && bundle exec rake $RAKE_TASK`
Make travis install libpcap-dev 2013-02-19 21:41:31 +00:00
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 14:29:44 +00:00			`rvm:`
Disable CI testing on 1.8.7 for now To stop the flood of everything-is-broken emails 2012-11-08 02:53:55 +00:00			`- '1.9.3'`
Add ruby 2.x to travis testing 2014-09-08 02:55:13 +00:00			`- '2.1'`
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 21:02:09 +00:00
			`notifications:`
			`irc: "irc.freenode.org#msfnotify"`

Attempt to make travis useful again Lowers the history depth from the default of 100. 2013-01-24 21:48:04 +00:00			`git:`
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 22:23:16 +00:00			`depth: 5`