EMC compile farm wrote:
> Target: emc2head
> System: Ubuntu 8.04 LTS (hardy) realtime (2.6.24-16-rtai)
> Date: 2008-11-08 06:44:09 (complete build)
> Result: PASS
>
> Build log:
> http://linuxcnc.org/compile_farm/emc2head_slot4_log.txt
>
> Complete compile farm results:
> http://linuxcnc.org/compile_farm/index.shtml
Looks like I'm continuing my tradition of duplicating John Kasunich's
work... When I didnt hear back about setting up an 8.04 builder, i
raised a second robot army:
<http://nappy.colorado.edu/buildbot/waterfall>
This system uses BuildBot, from <http://buildbot.net>.
The "waterfall" page linked above shows the current status and history
of the build farm. There is one column per "thing being built". Time
goes from "recent" at the top of the page, to "older" as you go down.
There are two "buildslaves". A buildslave is a computer capable of
building the software. This is analogous to "farm slots" in JMK's
Compile Farm. My two buildslaves are "Dapper x86 with RTAI" and "Hardy
x86 with RTAI", both installed via the LiveCDs from linuxcnc.org. Each
buildslave is a QEMU/KVM virtual machine that can run pretty much
anywhere. The buildbot will happily do parallel builds if multiple
identical buildslaves connect. I have it set up to do no more than one
build at a time on each of the buildslaves, that's why the waterfall
display looks so staggered.
There are three "build factories". A build factory is a set of commands
to accomplish a build, analogous to the "emc2_build" and
"emc2_build_sim" programs in the farm-scripts. The three I have are:
sim, realtime-rip, and realtime-deb. The exact steps taken for each are
shown in the link above.
I'm currently building Trunk and 2.2 with each of the three build
factories, on each of the two buildslaves, for a total of 12 builds.
Everything is working, except the realtime-rip build-factory runs the
runtests script at the end, and that's failing on all four combinations
of CVS-source and build-slave.
One nice thing about the buildbot architecture is that it doesnt require
any build-slave updates to change the build scripts. The buildslaves
get their instructions from the build master on a per-build basis.
Adding new build factories or changing existing build factories is a
server-side-only operation; the next time the build master sends a build
request to a build slave, the new instructions will be sent.
Anyway, that's what I did last week. I was running the build master and
both the slaves on my laptop for development, but when I saw the new and
improved builds coming from JMK's Compile Farm I quickly put it up on
the web where y'all can see it. That's also why the build master shows
only one build so far - i nuked the history when i moved it to the new
server.
If this is deemed useful i'll be happy to keep working on it and
maintain it. If so it'd be great if people could help run the
buildslaves. They're QEMU/KVM appliances, all they need is a couple of
gigs of disk space, access to the CVS repo for anonymous checkouts, and
the ability to make TCP connections to the build master. I'd like to
run several instances of each buildslave, so that the build can go on
even if some slaves go down.
I also want to add amd64 buildslaves, are there any LiveCDs for amd64
emc2 installations?
--
Sebastian Kuzminsky
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
