Skip to content

Commit

Permalink
Cut rake out of rspec/cucumber for CI builds.
Browse files Browse the repository at this point in the history
When something environmental fails (i.e. not in an individual spec, but when the spec files are being loaded), the rake tasks craps out but does not include the backtrace of what failed.  It's really annoying and hard to troubleshoot.  This should work better.
  • Loading branch information
myronmarston committed May 4, 2012
1 parent 1bdaa8c commit 2ac7a03
Show file tree
Hide file tree
Showing 2 changed files with 15 additions and 1 deletion.
2 changes: 1 addition & 1 deletion .travis.yml
@@ -1,7 +1,7 @@
language: ruby
env: CUCUMBER_FORMAT=progress
bundler_args: --without extras
script: "bundle exec rake ci:build --trace"
script: "script/ci.sh"
rvm:
- 1.8.7
- 1.9.2
Expand Down
14 changes: 14 additions & 0 deletions script/ci.sh
@@ -0,0 +1,14 @@
# Kill the whole script on error
set -e

# Setup vendored rspec-1
git submodule init
git submodule update

bundle exec ruby -w -I./spec -r./spec/capture_warnings -rspec_helper -S rspec spec --format progress --backtrace

bundle exec cucumber

bundle exec rake yard_coverage

bundle exec rake check_code_coverage

0 comments on commit 2ac7a03

Please sign in to comment.