On Nov 30, 2007 8:35 PM, DHH <[EMAIL PROTECTED]> wrote: > > I think, it does make sense to run migrations in the continuous > > integration loop (but not in the local build). Reason: you want to > > test them > > I don't think I understand this. Why do you want or need to > continuously test the migrations?
I'm not sure the "continuous" that Alexey was referring to was the CI process (as in: it is always running), or a repeated run of every migration each time the test suite is run. The former certainly makes sense; you'd want to test that a migration can successfully run based solely on the contents of the SVN repository and other expected artefacts; verifying that it won't fail because a developer has failed to commit or add a particular file before you try and run that migration on the production system. That is, you'd want to test that any new migrations don't cause a system failure - not that every migration can be run, each time the CI system runs against a new build. -- * J * ~ --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
