Permalink
Browse files

don't require ci_reporter in the cc in production

In prod, the cloud controller rakefile is used when running
migrations, i.e. bundle exec rake db:migrate, so
we can't require ci_reporter from the rake file as that gem
won't have been installed since it is only installed as
part of the test group.

Note that this is the only component that we need the rakefile
for in prod, so it is the only one that needs such an update,
which is good, because there isn't a standard way to tell if
the DEA's, Rotuer's, etc. rakefiles are being invoked in
in prod or test mode.

Change-Id: I92af1cd18f0f5f03c4407cf7751265114bc770d3
  • Loading branch information...
1 parent 74c5b49 commit aa9a6dbcdc0a287da3cd3e858a8d1e2f04fe33e6 Patrick Bozeman committed Jan 3, 2012
Showing with 1 addition and 1 deletion.
  1. +1 −1 cloud_controller/Rakefile
@@ -1,5 +1,5 @@
require File.expand_path('../config/application', __FILE__)
-require 'ci/reporter/rake/rspec'
+require 'ci/reporter/rake/rspec' if Rails.env != 'production'
CloudController::Application.load_tasks

0 comments on commit aa9a6db

Please sign in to comment.