Cruisecontrolrb users - Aug 2008 - edits to database.yml make builds fail

Hi,

We''re seeing an issue where edits to database.yml - even edits that
don''t affect environments/branches being monitored with
cruisecontrolrb - cause builds to fail.

Running "svn revert" on database.yml in the build tree fixes the
builds, oddly enough.

Can someone, quick-and-dirty, explain what causes this, so that we
better understand why it breaks our builds?  :-)

thanks,

--elijah

On Mon, Aug 18, 2008 at 12:01 PM, elijah wright <elijah.wright at
gmail.com> wrote:
> We''re seeing an issue where edits to database.yml - even edits
that
> don''t affect environments/branches being monitored with
> cruisecontrolrb - cause builds to fail.
Can you give more detail on the failures?

Could it be to do with the development database you''re pointing to in  
your database.yml?

I had some issues - mostly due to my naivety with the rails framework  
- around what happened to database schemas when the rake tasks ran to  
run our tests - it was stomping over the CI environment''s test  
database with the schema from somewhere else...

hope that''s helpful...
Matt

On 18 Aug 2008, at 20:01, elijah wright wrote:
> Hi,
>
> We''re seeing an issue where edits to database.yml - even edits
that
> don''t affect environments/branches being monitored with
> cruisecontrolrb - cause builds to fail.
>
> Running "svn revert" on database.yml in the build tree fixes the
> builds, oddly enough.
>
> Can someone, quick-and-dirty, explain what causes this, so that we
> better understand why it breaks our builds?  :-)
>
> thanks,
>
> --elijah
> _______________________________________________
> Cruisecontrolrb-users mailing list
> Cruisecontrolrb-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users

Elijah,
Do you have modifications in the cruise project''s work directory (for
example to point it at a different DB) that are leading to svn
conflicts?

I know you said it was happening with changes to environments that
cruise doesn''t care about, but I''ve definitely seen pain
result from
team members "solving" environment inconsistency problems by changing
some environment config directly on the cruise server. (Don''t do
that.)

-hume.

On Mon, Aug 18, 2008 at 4:20 PM, John D. Hume <duelin.markers at
gmail.com> wrote:
> Elijah,
> Do you have modifications in the cruise project''s work directory
(for
> example to point it at a different DB) that are leading to svn
> conflicts?
>
> I know you said it was happening with changes to environments that
> cruise doesn''t care about, but I''ve definitely seen pain
result from
> team members "solving" environment inconsistency problems by
changing
> some environment config directly on the cruise server. (Don''t do
> that.)
Yep.  To avoid this, you can leverage ERB to either have conditionals
based on hostname, or read proper values from ENV variables or
svn:ignored custom config files..