Early access builds

Mark Wielaard mark at klomp.org
Wed Jun 10 07:52:33 UTC 2009

On Mon, 2009-06-01 at 05:55 +0200, Mark Wielaard wrote:
> On Sun, 2009-05-31 at 14:20 -0700, Kelly O'Hair wrote:
> > Effectively what I'm thinking is a kind of cleanroom build of an openjdk
> > forest, using Fedora 9 X86 32bit, and OpenSolaris X86 32bit to start.
> > I'll create a simple self-extracting tarball installer (no rpm/deb/ips packages),
> > and publish them in a public openjdk area.
> > No testing to start, but adding testing with published results could
> > be done by just about anyone.
> > If I do this right, we can in theory point at any openjdk project forest
> > and provide the same build service for any project.
> That sounds like a wonderful start!

So I hacked together a quick script this weekend to do this for the
IcedTea repos (attached below). It has been running for a couple of days
now. It isn't the most shiny solution. But I wanted something that just
worked for now. In the future we can think about extending it with fancy
frontends (maybe hudson integration to show jtreg results). For now it
just sits there looping through the repositories checking every 15
minutes whether there have been updates (this should of course be
triggered by a commit hook some day) and then does an autogen.sh &&
configure && make && make check reporting any build failures or changes
in test results it finds on the way (it reports them to everybody that
made a change since it last checked, if that gets annoying please yell
and we change it to only report to the mailinglist). Then it dumps the
build, sources and test results (including all .jtr files so you can
easily compare) at:


Hope that is useful and can be extended to other repositories.

It currently only has space for one build per repository. And sadly has
to dump the documentation and debuginfo for now to preserve space. The
build is done in a Debian Lenny i686 chroot environment. Which should
produce binaries that run on most x86 GNU/Linux systems (Debian Lenny
was chosen since it has both a pretty old glibc, but also a new enough
gcj to bootstrap everything out of the box - well ok, and because the
host was already running a x86_64 Debian etch variant, so setting up a
lenny i686 chroot was pretty easy.).



More information about the discuss mailing list