On Sun, 2009-11-15 at 21:45 +0100, Lieven Govaerts wrote:
> > Given our familiarity with it, I think it makes sense to stick with
> > buildbot. That said, I like Hudson and we have done some work
> > recently so that our build and test can integrate nicely. For
> > example, Hudson can display the test results a lot more nicely and
> it
> > graphs things like the execution time that can help spot trends. I
> > personally prefer buildbots red/green model over Hudson's "weather
> > report".
> >
> The execution time of tests is (somewhat) visible in Buildbot's
> waterfall view, but I don't see that as a compelling feature. Are
> there any specific features in Hudson that you'd want that are not in
> Buildbot?
We've the Hudson setup for Subversion build process. Hudson provides
many reports that I'm not sure if buildbot provides:
a) Test time trend report
b) Plugin to check the python coding semantics using pylint
c) Plugins for code coverage, Clover, Cobertura. I'm not sure if it has
support for any code coverage tool for C/Python though
d) ... and many more plugins that might be useful for this build process
It is easier to manage jobs in Hudson while we have to create new builds
for every new releases.
As Greg suggested, we should try both the build systems to leverage the
benefits, until we decide upon anyone. I shall co-ordinate the setup for
Hudson, if we decide to do so.
--
Bhuvaneswaran A
CollabNet Software P Ltd. | www.collab.net
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2418355
Received on 2009-11-16 08:50:40 CET