Continuous builds

Mark Doliner mark at kingant.net
Tue Sep 9 13:06:35 EDT 2008


2008/9/9 Richard Laager <rlaager at wiktel.com>:
> On Tue, 2008-09-09 at 16:21 +0100, Phil Hannent wrote:
>> 1, Are the Pidgin developers interested in using buildbot?
>
> I think it'd be useful for continuous integration testing... In other
> words, making sure everything actually builds correctly.

Fer sure.  There's also a thing called bitten
(http://bitten.edgewall.org/build) that integrates with closely with
trac.  We don't know how well it works.  But if you definitely need
buildbot for work then it doesn't really make sense for you to look at
bitten.

>> 2, If not are you OK with me releasing nightly builds?
>
> I don't think there's a huge need. We release pretty frequently. Nightly
> builds are more likely to be broken than useful.

As a whole I think we're mostly OK with you releasing nightly builds.
We certainly wouldn't be able to stop you if we actually wanted to :-)
 Personally I'm in favor of nightly builds.  I think they'll encourage
development just the slightest bit, and I think they could be useful
when there are times that we think we fix a bug and what a user to
test it.

Please make sure you keep a local copy of the repository and mtn pull
to update it (rather than grabbing the entire thing from scratch each
night).

The way I've created RPMs in the past is by checking out a clean copy
of the source, running ./autogen.sh, running make dist, then building
the RPM with something like "rpmbuild -ta pidgin-2.5.3dev.tar.gz"

I don't know the process for building debs.  We've never done those
ourselves--Debian and Ubuntu have always done it, and they have their
own build files that they maintain themselves.

-Mark




More information about the Devel mailing list