Sun enters the Continuous Integration business

Posted on August 4, 2009 by Julian Simpson

Sun sell a Continuous Integration server. We should have seen that one coming. See Kohsuke Kawaguchi’s announcement. Looks like you buy it as an add-on to the GlassFish stack. Pricing is here. Looks like they’ll support a branch of Hudson, and not the open source releases. That’s not unexpected.

Strategically, it seems like a good idea. They’ve been building their own stack for years, from operating system to web server. Sun just pimped it with a very popular Continuous Integration server. I think It’ll be a good proposition for Java shops. There’s a huge market for Hudson for other platforms, but I’m not sure that Sun will be chasing it.

(image by Silveira Neto)

Be Sociable, Share!

About Julian Simpson

Founder and Editor of The Build Doctor. Drinks Flat Whites. View all posts by Julian Simpson →

4 Responses to Sun enters the Continuous Integration business

Marco Abis says: August 5, 2009 at 1:07 am

This is really interesting, especially if read remembering the “Continuous Integration Doom and Gloom?” post

simpsonjulian says: August 5, 2009 at 11:39 pm

Yep. And there’s more interesting news

Eduardo Pelegri-Llopart says: August 6, 2009 at 5:59 am

Hi Julian.

A couple of follow-ups on your post.

re: “they’ll support a branch of Hudson, and not the open source releases.” – We support 1.312 through a series of path releases that only contain the bug fixes. The fixes that go into the patches will be integrated into the main trunk.

re: “I think It’ll be a good proposition for Java shops. There’s a huge market for Hudson for other platforms, but I’m not sure that Sun will be chasing it.” – Hudson needs a Java container to run but it will support development in many platforms (and languages), and Sun supports that. For practical purposes, if you find a bug on Hudson, we want to be able to reproduce it in our container (GlassFish). If the bug is in, say, JBoss, we don’t want to _commit_ to fixing JBoss (or finding a complicated workaround for it); but we will certainly try to address it.

Hope this helps,
– eduard/o