this is a known bug in cruise, if you grab the latest from head, it should be fixed. it will also be fixed in the next release if you'd like to wait<br><br><div><span class="gmail_quote">On 5/23/07, <b class="gmail_sendername">
Christos Zisopoulos</b> <<a href="mailto:christos@42linesofcode.com">christos@42linesofcode.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi there,<br><br>When using a custom rake_task or when defining the default 'cruise'<br>task in my Rakefile I get into a peculiar situation. The rake task<br>runs in the 'test' environment which I define for most of the part,
<br>but not always...<br><br>If I have a task that depends on "test:db:prepare" then for some<br>weird reason the test:db:prepare" is executed in 'production' or<br>whatever environment cruisecontroll is running in. I think I traced
<br>it down to the fact that at the end "test:db:prepare" depends on the<br>default :environment Rake task which reads:<br><br>task :environment do<br> require(File.join(RAILS_ROOT, 'config', 'environment'))
<br>end<br><br>This is what my custom task looks like<br><br>task :cruise => "test:db:prepare"<br> # Do whatever here should first invoke test:db:prepare<br>end<br><br>Any ideas what might be the problem?<br>
<br>Cheers!<br>-christos<br>_______________________________________________<br>Cruisecontrolrb-users mailing list<br><a href="mailto:Cruisecontrolrb-users@rubyforge.org">Cruisecontrolrb-users@rubyforge.org</a><br><a href="http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users">
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users</a><br></blockquote></div><br>