Building on SVN commit would be nice but probably complicated to set up. Setting Continuum to poll hourly should ensure that failing tests are caught quickly enough.
The important task here is getting the tests right. Does anyone want to work on that? If not, I may this weekend. -Turadg On 1/17/07, Scott Cytacki <[EMAIL PROTECTED]> wrote: > > So we do have continuum which already runs tests after the code has been > committed. This will be the easiest way to run to the tests. > > But I agree it would be best if code could not be committed if it fails > tests like these. > > Scott > > On Wed, 2007-01-17 at 12:07 -0500, Stephen Bannasch wrote: > > In a TELS discussion yesterday I wondered whether we could use > > Subversion pre-commit hooks to run various test before the commit. > > > > The problem being that updates to various jars were making existing > > curnits invalid. It would be good to have a set of tests a developer > > could run before committing. To make this more reliable I wondered if > > the tests could be automatically applied. > > > > For security reasons they only make a few scripts available which are > > documented here: > > > > http://sourceforge.net/docman/display_doc.php?docid=31070&group_id=1#scripts > > > > None of these would allow us to run tests. Sourceforge will look at > > additional script requests. > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" 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/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
