BT

Your opinion matters! Please fill in the InfoQ Survey!

Hudson Moves to GitHub (Again)

| by Alex Blewitt Follow 2 Followers on Feb 14, 2011. Estimated reading time: 1 minute |

A note to our readers: As per your request we have developed a set of features that allow you to reduce the noise, while not losing sight of anything that is important. Get email and web notifications by choosing the topics you are interested in.

Whilst Jenkins 1.397 was released this weekend, Sonatype have backed Hudson for their users. Originally hosted at Java.net, the problems with the Kenai transition precipitated the original move of the community (and the codebase) onto GitHub, and ultimately the rebranding/fork of Jenkins from Hudson.

After the split, Oracle announced that Hudson would continue on the Oracle/Java infrastructure, as before. Sonatype, who have a commercial product based on Hudson, have stepped in to fill the void and have been commiting changes based on the Mavenization of Hudson.

Sonatype have experience in converting organically grown projects; Maven 3 is the work of many tests and refactorings to be built on a dependency injection framework (Guice) as covered by InfoQ last year. The same plan will apply to Hudson's migration, which though powerful, has forked copies of dependent libraries bundled inside its WAR. By modernizing the dependency mechanism, Sonatype hopes to make it easier for developers to contribute in the future. The Hudson-JSR330 GitHub fork contained the work that Sonatype had done (prior to the split) and now made public through the course of its evolution.

Now, it looks like Hudson's future is again back on GitHub after Jason van Zyl tweeted the results of the hudson-dev vote having received Oracle's Ted Farrell and Winston Prakash approval for the change. The Hudson name is available at github.com/hudson as the name was freed up after the Jenkins name change.

With the commercial support of both Oracle and Sonatype behind the development of Hudson, the future looks good for the eponymous continuous integration tool. However, Jenkins continues to evolve as well and it's likely that the two will drift apart over time. Ironically, although Hudson has kept the name, the refactorings to support JSR-330 and Mavenization of the build process represent far bigger changes than the ongoing and incrementally evolving Jenkins.

Rate this Article

Adoption Stage
Style

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Discuss

Login to InfoQ to interact with what matters most to you.


Recover your password...

Follow

Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.

Like

More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.

Notifications

Stay up-to-date

Set up your notifications and don't miss out on content that matters to you

BT