Great work! When it comes to hardware, I was kind of convinced that Django have been already using the snakebite network to access various platforms for builds testing (http://djangoninja.com/post/73799680/django-on- snakebite)
Isn't their network compatible? (more about SnakeBite: http://www.snakebite.org/) Jakub On Feb 26, 4:54 am, Eric Holscher <e...@ericholscher.com> wrote: > Hey everyone, > > During the sprints, I worked to set up a hudson instance for Django. This is > hopefully going to be the way that we are going to go forward for now with > doing continuous integration for Django. I have a pretty good setup going > currently, and want make it really fantastic. At this point in time, what we > really need now is some more hardware to be able to run tests on. > > The current setup is hosted at:http://hudson.djangoproject.com/ > > Currently, I have tests running on the following architectures: > > Django trunk: > > Solaris: > Python 2.4-2.5 > Databases: sqlite, postgres, mysql > > Ubuntu: > Python 2.5-2.6 > Databases: sqlite, postgres, mysql > > Django 1.1.X: > > Solaris: > Python 2.5 > Databases: sqlite, postgres > > This gives us pretty good coverage currently, but the whole point of doing > CI is that we catch bugs on other platforms we wouldn't normally run on. > > What we need > =========== > > So I'm looking for people who can offer other boxes that they would like to > see tested. Currently the big ones we aren't covering are Windows boxes, and > the Oracle backends. There are lots of other permutations that we could be > testing against (Different python runtimes being a good example). > > However, we don't want to get in a situation where boxes that people have > set up just disappear. So, I'm only currently looking for machines that > people would be able to dedicate to the effort. We would require a > django-testing user account on the box, with our SSH key on it. There would > also be a team of trusted users, who would have access to this key and thus > your machine. > > We want the build farm to be stable and useful, and in the past we have had > too much trouble having machines just disappear. > > Requirements > =========== > > Currently the hudson requirements seem to be about <1GB of disk space, with > 512MB of ram. I'm also looking into some pony build/barn based alternatives > that would knock the memory requirements down pretty substantially. However, > for the current 1.2 release it looks like hudson is how we're going to make > it going forward. > > Note that for $20/mo a 512MB machine can be run on Rackspace cloud, so > another way that we might be able to get this going is to be able to have > donations to the DSF, and have them get some dedicated rackspace boxes. > However, for now, I'm hoping that we can cobble together enough stuff to get > 1.2 tested really well. > > Feedback > ========== > > If you have any thoughts on CI, or any advice, I would love to hear it. I'm > trying to make our Continuous Integration setup really kick ass, so feedback > is necessary to do this. I have some notes and ideas that I have been > recording while setting things up over at the pycon etherpad: > > http://pyconpads.net/django-testing > > Let me know if you have any thoughts, questions, or concerns. > > Cheers, > Eric -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
