metasploit-framework/.travis.yml

bundler_args: --without coverage development pcap
cache: bundler
env:
  - RAKE_TASKS="cucumber cucumber:boot"
  - RAKE_TASKS=spec SPEC_OPTS="--tag content"
  - RAKE_TASKS=spec SPEC_OPTS="--tag ~content"

language: ruby
matrix:
  fast_finish: true
before_install:
  - "echo 'gem: --no-ri --no-rdoc' > ~/.gemrc"
  - rake --version
  # Fail build if msftidy is not successful
  - 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_TASKS
sudo: false
rvm:
  - '2.1.6'

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

git:
  depth: 5

# Blacklist certain branches from triggering travis builds
branches:
  except:
    - gh-pages
    - metakitty

addons:
  postgresql: '9.3'
Remove need for sudo MSP-11931 2014-12-31 19:25:48 +00:00			`bundler_args: --without coverage development pcap`
Cache bundle MSP-11931 2014-12-31 20:00:11 +00:00			`cache: bundler`
Add cucumber to test matrix MSP-11153 2014-08-27 21:50:25 +00:00			`env:`
Combine cucumber and cucumber:boot into one job MSP-11671 The run times for cucumber are so much faster now that `spec --tag content` is actually the slowest job (on 1.9.3). The job is so slow that the two cucumbers can be merged together and they will take the same time, but we'll consume 2 fewer job slots (1 for 1.9.3 and 1 for 2.1), so the longer per job time is better as long as it does become the longest job time. 2014-12-05 19:37:18 +00:00			`- RAKE_TASKS="cucumber cucumber:boot"`
			`- RAKE_TASKS=spec SPEC_OPTS="--tag content"`
			`- RAKE_TASKS=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 install documentation on travis-ci MSP-11671 Passs `--no-ri --no-rdoc` to gem. 2014-12-05 19:29:18 +00:00			`- "echo 'gem: --no-ri --no-rdoc' > ~/.gemrc"`
Don't try to bundle exec before bundle install 2014-01-06 18:47:36 +00:00			`- rake --version`
Add new comment about post-merge hook 2015-02-11 19:48:13 +00:00			`# Fail build if msftidy is not successful`
Reenable post-merge hook in Travis 2015-02-11 19:40:53 +00:00			`- 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`
Combine cucumber and cucumber:boot into one job MSP-11671 The run times for cucumber are so much faster now that `spec --tag content` is actually the slowest job (on 1.9.3). The job is so slow that the two cucumbers can be merged together and they will take the same time, but we'll consume 2 fewer job slots (1 for 1.9.3 and 1 for 2.1), so the longer per job time is better as long as it does become the longest job time. 2014-12-05 19:37:18 +00:00			`- git diff --exit-code && bundle exec rake $RAKE_TASKS`
Enable containerized builds MSP-11931 Disable the need for sudo to allow use of the faster docker infrastructure. 2014-12-31 19:26:35 +00:00			`sudo: false`
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:`
Travis should fix to 2.1.6 directly, no fuzziness 2015-05-07 18:44:31 +00:00			`- '2.1.6'`
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`
Travis shouldnt test gh-pages and friends This adds a blacklist of branches that Travis shouldn't run tests against. 2014-12-03 19:58:06 +00:00
			`# Blacklist certain branches from triggering travis builds`
			`branches:`
			`except:`
			`- gh-pages`
			`- metakitty`
Set postgres version for Travis to 9.3 2015-04-09 22:16:37 +00:00
			`addons:`
Travis should fix to 2.1.6 directly, no fuzziness 2015-05-07 18:44:31 +00:00			`postgresql: '9.3'`