Due to lack of response, I just went ahead and tried to setup a Trac + Bitten site to get a feel for it. It would seem that the test framework is dependent on the bitten unittest as replacement for the python unittest in order to get the test-results.xml produced and fed to the graphs. Mind you, I'm a python newbie, so I'm not sure how this works. The Trac+Bitten integration, however, seems to work nicely after adding a few trivial patches and a couple of robustness items to latest bitten from trunk.
I've got the following builds setup and available for viewing: o http://www.linadd.org/build/trac-svn o http://www.linadd.org/build/bitten-svn o http://www.linadd.org/build/genshi-svn A few more are on their way. Mind you, the repository used is my local one for the build configuration only, i.e. it is not connected to the real source repositories, which one would like to have at some point, I guess. Trac uses the native svn access interface, so the repository has to be on the same machine as Trac is using. I haven't tried it, but to my understanding, subversion has some repository synch tool built in in later versions, so that should be easy to fix when the day comes, simply by adding a one-way synch with a read-only repository at the end. For some of the above build projects, I had to add the following simple changes to setup.py and setup.cfg to get things working: For example, in trac-svn, I had to add the following to the "entry_points" definition in setup.py: [distutils.commands] unittest = bitten.util.testrunner:unittest Also in trac-svn, I had to add the following to setup.cfg: [unittest] xml-results = build/test-results.xml coverage-summary = build/test-coverage.txt coverage-dir = build/coverage Similar for genshi-svn. With these changes, i get the test and coverage results collected in a way that is suitable for bitten, and the test and coverage build graphs will magically appear. And I have to say, the Trac + Bitten combo looks real nice, and once setup, practically zero-maintenance. Now to the problem: how do I get the django tests to play along in this scenario? I.e., how do I get django to recognize and use the unittest from bitten.util.testrunner as stated above? I've fiddled around a bit in the django code, but to no avail. I do not understand python and setuptools sufficiently. Any ideas appreciated. /Lars On Jun 22, 1:17 am, stava <[EMAIL PROTECTED]> wrote: > On Jun 1, 5:15 pm, "Jacob Kaplan-Moss" <[EMAIL PROTECTED]> > wrote: > > > Hi folks -- > > > We talked about this a while back: Django really needs a buildbot (or > > some other continuous integration tool). I had planned to tackle this > > myself (usingBitten--http://bitten.cmlenz.net/) but it's getting > > clear I'm not going to get it done in any reasonable amount of time. > > > So, is there anybody out there who could get some sort of CI tool set > > up? I'd preferBittenbecause of the Trac integration, but Buildbot > > would be fine, as would anything else. > > > If you're interested let me know and I'll flesh out the details of > > what I'd want to be able to test. > > I'd be interested to help out using Trac +Bittenon some server(s) of > mine. Unfortunately, Cristopher Lenz just announced that he has > difficulties keeping up with the development ofBitten, especially to > adapt it to the latest changes in Trac. I'm not really a python > programmer, so that's a bit worrying. However, the Trac +Bittencombo > is a brilliant solution, and maybe there are python people that could > help out if need be. Let us know the details of what you're looking > for and we'll see what we can do. > > Cheers > /Lars Stavholm (http://www.linadd.org) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
