Bad form to reply to myself but... On 20/09/06, Matthew Flanagan <[EMAIL PROTECTED]> wrote: > Hi, > > I've noticed a couple of tickets with patches coming in for python > 2.5. As I mentioned in this thread [1], it might be useful for the > django project to get a buildbot builder or two going on a few of the > slaves at http://pybots.org. > > These can be used to test django against python 2.5 and 2.6. Python > 2.5 comes with pysqlite built in, though you still have to build the > actual sqlite3 binaries too, so this would make it quite easy to run > the tests against that. A more advanced buildbot builder might run the > tests against all the database backends that django supports. > > The advantage of this is even better user visibility and confidence > that the django trunk is stable. > > To do this properly really requires someone with admin access to > code.djangoproject.com so they can set up the post-commit hook to > notify the buildbot slave to run the tests.
Nothing needs to be done by the django admins as the test builds are only triggered by commits to the python repo not the django one. So perhaps I might find some time to get this going. > > I am using buildbot internally at my company to test our OS & > application baremetal installation system, which has dozens of unique > application builds and is all driven from a django frontend. > > [1] > http://groups.google.com/group/django-users/browse_thread/thread/7a7b8f5a1b63012b > > opinions? takers? > > regards > > matthew > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
