Do you intend to setup the continuous integration server to run rake tests against the 3 supported DB types or run the tests against sqlite3 in-memory? How about testing migrations from the last previous released version?
On 5/2/07, Luke Melia <[EMAIL PROTECTED]> wrote:
BSAG wrote: > [Raises her hand...] A very stupid question from the back here, but what > exactly is a continuous integration server? Apart from a server which > continuously integrates ;-) I think I might need a wee tutorial. Your guess is amazingly spot on! :) Here's are two good pieces on the subject: http://confluence.public.thoughtworks.org/display/CCNET/What+is+Continuous+Integration http://www.martinfowler.com/articles/continuousIntegration.html The main thing it would mean for Tracks is to publicize the pass/fail status of tests on a standard build, and automatically be creating the package we will ultimately distribute. We would strive to automate and include all steps that would otherwise be manual in the preparation of a release. I'm planning on using rake tasks and cruisecontrol.rb <http://cruisecontrolrb.thoughtworks.com/> as the engine behind this. Cheers, Luke
_______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
