schema.rb is a generated file. It's constructed from your development database structure, and used to create the test database every time you run tests. Although I've seen people argue that you should leave it, in my version control world generated files are never checked in to the repository.
You should: 1. delete it from your subversion repository 2. tell svn to ignore it After those two steps, your builds should run more smoothly. Regards, Lori On Wed, Apr 30, 2008 at 11:16 AM, Will Sargent <[EMAIL PROTECTED]> wrote: > This is interesting, and I'm still not exactly sure what's causing it. > > When people check in files, occasionally CruiseControl will error out > saying that there's a conflict in schema.rb. I can go into > cruisecontrol and svn revert the file, but it's cropped up several > times, and I'm getting a little tired of it. > > How does schema.rb work? I've read through The Rails Way and some > online references, but I still don't really think I understand how > Rails, integration testing and database migration all interact. > What's the usual cause of this, and is there some series of steps in > CruiseControl or rake that prevents this happening? > > Will. > _______________________________________________ > Cruisecontrolrb-users mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users >
_______________________________________________ Cruisecontrolrb-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
