Volunteer(s) needed: Django needs a buildbot
Jacob Kaplan-Moss
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 (using Bitten -- 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 prefer Bitten because 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.
Thanks!
Jacob
Massimiliano Ravelli
wrote:
> So, is there anybody out there who could get some sort of CI tool set
> up?
I have a very simple installation of buildbot.
At every commit the build-slave checks out the source of my django
apps,
runs the tests and builds debian packages.
If you don't find more experienced users I can try to help you.
I can also setup a linux/python2.4 build-slave for django.
Moreover, I'm going to install a few virtual machines which could
test
django on different SO/configuration (but no mac nor windows).
> I'd prefer Bitten because of the Trac integration, but Buildbot
> would be fine, as would anything else.
Trac integration is very interesting, but, sorry, I don't know Bitten.
Hi
Massimiliano
Henrik Levkowetz
On 2007-06-04 09:53 Massimiliano Ravelli said the following:
I've done a good-enough-to-start-with integration of Trac and BuildBot
for another project (which also uses Django). There's one plugin file
for Trac, which takes care of the menubar integration and pulling the
pages from BuildBot, and one .py file for the Buildbot which provides a
modification of the waterfall status target, in order to provide commit
links to Trac's changeset view. Works well here. I'll clean up the
code and place this on Trac Hacks (trac-hacks.org) within a day or so.
Henrik
Massimiliano Ravelli
> I've done a good-enough-to-start-with integration of Trac and BuildBot
This is good news ! Let me know when the code is available.
Thanks
Massimiliano
Jason Sankey
wrote:
> We talked about this a while back: Django really needs a buildbot (or
> some other continuous integration tool). I had planned to tackle this
> 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 prefer Bitten because of the Trac integration, but Buildbot
> would be fine, as would anything else.
I am happy to offer an open-source license for Pulse:
http://zutubi.com/products/pulse/
it you are interested. Pulse is a commercial tool but we offer no-
strings licenses to open source projects for free. Given we have
benefited from Django when building our website, I'm also happy to
help with setup plus extra features (like integrating the results from
doctest/unittest -- something I have been keen to add for a while).
If you need it, we can even arrange basic hosting.
Pulse has Trac integration already, but only in one direction: Pulse
links changeset information to the relevant views (e.g. diff view) in
Trac. Plugging in the other way should also be possible by pulling out
information via the XML-RPC remote API.
> If you're interested let me know and I'll flesh out the details of
> what I'd want to be able to test.
Let me know if you would to try out Pulse. No matter if you prefer
another option, but the offer is there.
Cheers,
Jason
Michael Radziej
On Fri, Jun 01, Jacob Kaplan-Moss wrote:
> 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 (using Bitten -- http://bitten.cmlenz.net/) but it's getting
> clear I'm not going to get it done in any reasonable amount of time.
what would you exactly like the buildbot to do? Just follow svn checkins
and run the testsuite for all the database backends on pyton 2.3-2.5?
How should errors be reported, would an email to django-developers be
enough?
I don't see the need for sophisticated software like "bitten". We don't
need any distributed build or any dependency tracking, and not even
track integration if the reporting is independent.
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
Vorstand: Ingo Kraupa (Vorsitzender), Joachim Astel, Hansjochen Klenk -
Vorsitzender des Aufsichtsrats: Stefan Schnabel - AG Nürnberg HRB 17689
stava
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
> 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 prefer Bitten because 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 + Bitten on some server(s) of
mine. Unfortunately, Cristopher Lenz just announced that he has
difficulties keeping up with the development of Bitten, 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 + Bitten combo
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)
stava
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 <lars.stavh...@gmail.com> wrote:
> On Jun 1, 5:15 pm, "Jacob Kaplan-Moss" <jacob.kaplanm...@gmail.com>
> 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