Thibaut...
Thanks, but I don't think this is what's happening. I say that because
my database.yml has the configuration entries for all three db
environments. So even if it's not using the one I expect it to (TEST),
it should still be connecting to something, right?
Thibaut Barrère wrote:
>> Any thoughts on how to proceed?
>>
>
> Just one hint: the message could indicate that the RAILS_ENV you
> expect to be passed is not the right one, which would make the
> connection fails because database.yml would not contain the matching
> information.
>
> <snip>
> WARNING: with Rails projects, it is important that RAILS_ENV does not
> default to 'production'. Unless you want your migration scripts and
> unit tests to hit your production database, of course.
> CruiseControl.reb leaves this variable unchanged when invoking
> 'cruise' or other custom Rake task, and sets it to 'test' before
> invoking the defaults.
> </snip>
>
> regards
>
> -- Thibaut
>
>
_______________________________________________
Cruisecontrolrb-users mailing list
Cruisecontrolrb-users@...
http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
