and don't forget, developers make mistakes...all the time. if they didn't there would be little point to a continuous integration system in the first place. what if I change a migration, then "forget to run it" before checking in. this is exactly what ci should protect you from, however, in your case instead of just failing, ci will go into an error state that the only way to fix is to log onto the box.
no good. On Fri, May 2, 2008 at 9:57 AM, Billy Kimble <[EMAIL PROTECTED]> wrote: > There shouldn't be conflicts in that case. > There is a case where you may use migration 20, and then someone in your > team will use migration 21, so when you make a new migration you will use > 22. If the dev who used migration 21 did not check their stuff in yet, so as > far as your schema goes, you're up to version 22 ... but you're still > missing migration 21 until that person checks it in. > > > > -- > This message has been scanned for viruses and > dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is > believed to be clean. On May 2, 2008, at 9:48 AM, John D. Hume wrote: > > Can someone explain why you would expect to see schema.rb conflicts if the > checked in migrations are in sync with the checked in schema.rb? Wouldn't > you expect cruise to generate a schema.rb identical to the one checked in? > > > On Fri, May 2, 2008 at 2:44 AM, Jeremy Stell-Smith < > [EMAIL PROTECTED]> wrote: > > > it's still a generated file, and will still introduce conflicts on a > > system like cruise if you're running migrations on said system - because > > each time you do, it will regenerate a new copy of the file. > > > -- > This message has been scanned for viruses and > dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is > believed to be clean. _______________________________________________ > 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 > >
_______________________________________________ Cruisecontrolrb-users mailing list [email protected] http://rubyforge.org/mailman/listinfo/cruisecontrolrb-users
