[Cruisecontrolrb-users] Environment issues when using custom rake build task

[Jeremy Stell-Smith]

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

On 5/23/07, Christos Zisopoulos <christos at 42linesofcode.com> wrote:
>
> Hi there,
>
> When using a custom rake_task or when defining the default 'cruise'
> task in my Rakefile I get into a peculiar situation. The rake task
> runs in the 'test' environment which I define for most of the part,
> but not always...
>
> If I have a task that depends on "test:db:prepare" then for some
> weird reason the test:db:prepare" is executed in 'production' or
> whatever environment cruisecontroll is running in. I think I traced
> it down to the fact that at the end "test:db:prepare" depends on the
> default :environment Rake task which reads:
>
> task :environment do
>    require(File.join(RAILS_ROOT, 'config', 'environment'))
> end
>
> This is what my custom task looks like
>
> task :cruise => "test:db:prepare"
>    # Do whatever here should first invoke test:db:prepare
> end
>
> Any ideas what might be the problem?
>
> Cheers!
> -christos
> _______________________________________________
> Cruisecontrolrb-users mailing list
> Cruisecontrolrb-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20070523/708619a4/attachment.html