On 31/01/07, Marc Fargas Esteve <[EMAIL PROTECTED]> wrote: > > On 1/30/07, Michael Radziej <[EMAIL PROTECTED]> wrote: > > Marc Fargas Esteve: > > That sounds interesting. (Did I mention that it should run python > > versions 2.3, 2.4 and 2.5? ;-) > > As Matthew said this could be done with separate buildbots or slaves > running different jobs. > > > I wouldn't mind doing this on my own computer if it's so easy ;-) > It depends on how Matthew's buildbot works, normally if you have svn > and the required dependencies it just requires a few files and the > buildbot package, the hard work is at the master which, at the most > part, has already been done by Matthew (get the source, set a project, > test it...) >
I don't control the pybots master just the slave that does the django builds. The master is responsible for telling the slaves what to build. For pybots it triggers a build whenever any of the python developers commit changes to either the python 2.5 maintenance branch or 2.6 trunk. So only those python versions are available to test against on pybots. Take a look at my build slave test scripts at: http://pybots.googlecode.com/svn/trunk/slave/flanagan-sparc/ and the pybot master config at: http://pybots.googlecode.com/svn/trunk/master/community.cfg Adding more backends would just be a matter of creating a Django-mysql.sh, Django-postgresql.sh, etc scripts to run each backend test as distinct stages. > Then you can make your computer be a new "slave" that received build > jobs from the "master", then the master decides when your slave has to > do things. > > > 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. > > For that to be done the user would need all the different python > versions and backends (with the required database servers) to run it. > A user can already run the tests with one python version and database > or more if he/she has them. But it's not an easy thing to package, > that's why buildbot was written! > > > 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. > > Buildbot was written for that, the svn repository can tell the > buildbot when a new checking has been done and start a new bunch of > jobs against it. Having this in place the part of taking patches from > trac is not so hard, the problem is to identify which is the correct > patch to test. > > > Michael > Marc > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
