I guess I have absorbed a bit of the agile development philosophy, or maybe I am a sucker for automatically generated status displays, but whatever the reason, we now have a Buildbot running: http://buildbot.ghz.cc/public/nut/ The idea is that anytime someone checks a new SVN revision into NUT, the buildbot master will ask the slaves to check out the changes and build NUT. Since the build process consists of a 'make distcheck', we end up with a SVN snapshot with ./configure already built. This should help new users who might not have all the autotools installed. At the moment, the buildbot slaves are the ragtag collection of computers I have lying around the house. I am still working on a umask problem with the generated tarballs, but eventually, you will be able to click on the tarball link and grab whatever just got built. The only one that you should expect to be on continuously is the G4 Cube in the first column. Any volunteers to add to the "botnet"? All you need is Python and Twisted (I think); everything else gets pushed over the network. The machine doesn't have to be directly accessible from the Internet - the slave buildbot process connects back to the master whenever the slave machine is up. This would be a great way to make sure that things checked in to the trunk don't break Solaris, for instance. Contact me off-list for details on setting up a slave. The main Buildbot web site: http://buildbot.sourceforge.net -- - Charles Lepple
On 4/8/07, Charles Lepple <clepple@gmail.com> wrote:> I guess I have absorbed a bit of the agile development philosophy, or > maybe I am a sucker for automatically generated status displays, but > whatever the reason, we now have a Buildbot running: > > http://buildbot.ghz.cc/public/nut/ > > The idea is that anytime someone checks a new SVN revision into NUT, > the buildbot master will ask the slaves to check out the changes and > build NUT.Nice. :) -- Carlos Rodrigues
On 4/7/07, Charles Lepple <clepple@gmail.com> wrote:> Since the build process consists of a 'make distcheck', we end up with > a SVN snapshot with ./configure already built. This should help new > users who might not have all the autotools installed.Slight correction: it runs 'make distcheck-light'. Eagle-eyed readers may have noticed this in the logs already :-) e.g.: http://buildbot.ghz.cc/public/nut/Debian-etch-PowerPC/builds/25/step-compile/0 Essentially, the more packages you have installed, the more coverage testing we do. But I understand that some platforms don't need HAL (it's probably not going on my Mac OS X machine anytime soon), and not having a given package also verifies that the autoconf tests work in the absence of that package. -- - Charles Lepple
[adding back the list since Peter is the reference on such subjects...] 2007/4/13, Doug Reynolds <mav@wastegate.net>:> Arnaud Quette wrote: > > > since Charles is on the holidays road, I'm taking the mic. > > strange problem, that seems restricted to your fbsd system. > > AFAIK, it seems to be so. > > > I've just tested it again, both on a make dist'ed archive, and one of > > my local trunk. Everything works like a charm. > > > > Is the fdi file present in your tree otherwise? > > can you forward me the config.log associated, along with the version > > of HAL on your system. > > I've upgraded hal to: > > hal-0.5.8.20070403 Hardware Abstraction Layer for simplifying device access > > my autoconf is ver 2.61 > > Here is what the trouble is that the trunk/scripts has all the goodies, but they aren't getting copied to the build directory....:so the problem lies here. what about the make distdir from the top level. the output might show us the problem... since I really have no idea of what can cause that!> drwxr-xr-x 6 root wheel 512 Apr 12 17:58 .svn/ > drwxr-xr-x 3 root wheel 512 Apr 12 17:58 HP-UX/ > -rw-r--r-- 1 root wheel 16101 Apr 12 17:59 Makefile > -rw-r--r-- 1 root wheel 431 Apr 12 17:58 Makefile.am > -rw-r--r-- 1 root wheel 16086 Apr 12 17:59 Makefile.in > -rw-r--r-- 1 root wheel 168 Apr 12 17:58 README > drwxr-xr-x 3 root wheel 512 Apr 12 17:58 RedHat/ > drwxr-xr-x 3 root wheel 512 Apr 12 17:58 Solaris8/ > drwxr-xr-x 3 root wheel 512 Apr 12 17:58 Windows/ > drwxr-xr-x 3 root wheel 512 Apr 12 17:58 hal/ > drwxr-xr-x 3 root wheel 512 Apr 12 17:59 hotplug/ > drwxr-xr-x 3 root wheel 512 Apr 12 17:58 misc/ > drwxr-xr-x 3 root wheel 512 Apr 12 17:58 subdriver/ > drwxr-xr-x 3 root wheel 512 Apr 12 17:59 udev/ > > the trunk/nut-2.1.0/scripts is missing the hal (and others) > > total 22 > drwxr-xr-x 2 root wheel 512 Apr 12 17:59 HP-UX/ > -rw-r--r-- 1 root wheel 431 Apr 12 17:58 Makefile.am > -rw-r--r-- 1 root wheel 16086 Apr 12 17:59 Makefile.in > -rw-r--r-- 1 root wheel 168 Apr 12 17:58 README > > > > note that I've requested a new build on your system. > > > not a problem... >still pending. I've not much looked at bb, but you might need to allow the build. Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource Developer - http://arnaud.quette.free.fr/
Hi Doug, according to the bb report, the build has finally succeeded!? what was the problem? Arnaud -- Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/ Debian Developer - http://people.debian.org/~aquette/ OpenSource Developer - http://arnaud.quette.free.fr/