Marc Fargas Esteve:
> On 1/30/07, Michael Radziej <[EMAIL PROTECTED]> wrote:
> [..]
>> I'm now dreaming of a test service that would automatically run the
>> testsuite for a given patch (or multiple patches) with all supported
>> database backends ...
> 
> Also thought about that, getting up a buildbot for testing the SVN is
> not hard (it's already done on pybots), running the testsuite for a
> given patch has a big danger: One could upload a malicious patch just
> to f**k the buildbot. Some way would be needed to tell the buildbot
> that a patch is to be tested, then it only has to download the patch
> from a ticket and start a Build jobs.

That sounds interesting. (Did I mention that it should run python
versions 2.3, 2.4 and 2.5? ;-)

I wouldn't mind doing this on my own computer if it's so easy ;-)

> I could setup the buildbot for testing if it seems to make sense (most
> of the work is already done on pybots, only playing with all the
> possible combinations is needed).

Perhaps you can pre-build such a thing ready to download for
everybody who is interested? It's probably easier than building a
shared buildbot with proper authentication etc. Don't make any
complicated patch-auto-selection, let the user prepare the source,
and the buildbot runs the testsuite with all backends and the python
versions.

This could be used to test the trunk with each checkin (or daily),
or to test all the patches in stage "Ready for checkin". And I'd
love to have this for triage.

Michael


-- 
noris network AG - Deutschherrnstraße 15-19 - D-90429 Nürnberg -
Tel +49-911-9352-0 - Fax +49-911-9352-100

http://www.noris.de - The IT-Outsourcing Company

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to