The slides are available here.
JavaOne is just a few days ahead now, so let me recap what's happening around Hudson during JavaOne.
On Sunday, we have Unconference (RSVP) and a party at the Thirsty Bear (RSVP to "RSVP-ThirstyBear2009 at sun dot com".) The great thing
I run a budget-less Hudson cluster, just like many of you do, and one of the challenges is to have enough computing resources in a cluster.
Here's the problem statement.
Continuous Integration often requires a heterogeneous environments; for example, the GlassFish build requires Linux, Solaris, and Windows, and the JDK build requires something like 10 different environments, each carefully created so that we can test what we need to test.
Unfortunately, heterogeneous environments reduce the resource utilization — you can easily have some Windows slaves
Hudson Selenium plugin, which instantly lets you deploy Selenium
Grid on top of your existing Hudson cluster. By using this plugin, you
can start using Selenium Grid without installing it on individual
machines in the cluster manually.
Whether you recycle old PCs or use new ones as Hudson slaves, you have to first install an OS on a system. As the Hudson cluster I managed gets bigger, I find this more and more painful.
Japan is in the middle of a week long holiday this week, so our Japanese Hudson committers are cranking out a lot of cool stuff.
This one is from Kiyotaka, who wrote a Hudson plugin called GCrawler.
GCrawler (1) searchs Google Code and discovers all Grails projects, (2) reads Subversion repository to figure out metadata, and
This is from Seiji Sogabe, who is a Hudson committer. He put together a chart of the hudson.war size from 1.100 to 1.300.
"You can do everything from GUI" has always been one of Hudson's strengths, and we also have the REST API, but at the same time, CLI is also very useful for improving automation around administration, builds, and so on. So starting Hudson 1.302, I added a CLI agent to Hudson.