icedtea server mercurial upgrade

Mark Wielaard mark at klomp.org
Sun Mar 6 14:56:11 PST 2011


Hi,

The ancient mercurial instance on the main icedtea server
and the backup server have finally been upgraded to mercurial 1.8.
It was still using 0.95 before. This makes sure all the latest
mercurial features are supported. It also brings a fancy new
web frontend. All hgweb stores have been upgraded:

http://icedtea.classpath.org/hg/
http://icedtea.classpath.org/people/
http://icedtea.classpath.org/icedrobot/hg/

The graph view is pretty nifty.

Plus the backup server that hosts repositories from the above
three locations plus backups of the main openjdk ones:
http://icedtea.wildebeest.org/hg/
Backups are pulled every 30 minutes.

The new setup also means you should be able to create nested
subrepositories now under your people account. (But I think
they are slightly confusing, so I would caution against
them unless you really, really, really, think you need them.)

I had to make some small tweaks to the buildbot integration
(pushed upstream) and the hgforest extension. Since there is
no real hg forest upstream anymore, I collected patches from
various forks, plus our own, and put them in a new repository
that holds the code that is running on the server now and that
you can use on the client too:

http://icedtea.classpath.org/hg/hgforest/

But you should not need to upgrade your current setup,
unless you already had problems with the forest extension.
(Most fixes/changes are for server side issues with newer
versions of mercurial.)

As a bonus, the few lucky projects that are wired to the
buildbot, icedtea6, icedtea[7], icedtea-web and testrepo,
now trigger from the main server instead of the backup
server. Which means you can see the buildbot herd fire up
almost instantly after your commit (well, with a ~5 minute
delay and assuming the are free non-busy slaves).

http://builder.classpath.org/icedtea/buildbot/waterfall

As always, please yell and scream if this upgrade broke
some workflow. Apologies in advance if that did happen.

Thanks,

Mark




More information about the distro-pkg-dev mailing list