News

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

Jenkins First Release; Hudson Support

Posted by Alex Blewitt on Feb 03, 2011

Sections: Operations & Infrastructure,; Process & Practices,; Development
Topics: Java ,; Languages ,; Build systems ,; Architecture ,; Programming ,; Jenkins ,; Hudson

The first version of Jenkins has been published, along with a migration document for how to move from Hudson to Jenkins. Since it is distributed as a WAR file, the main noticable change is the jenkins.war name instead of hudson.war; though on UNIX systems, the runtime library location is /var/lib/jenkins instead of /var/lib/hudson. The run-as user has been renamed to jenkins as well.

The changelog lists only a few changes over the previous release:

Fixed a bug in crontab "day of week" handling in locales where a week starts from Monday. (issue 8401)

If a master fails to ping a slave, it should be hard-disconnected.

"java -jar hudson.war --daemon" was forcing umask 027. This includes Debian/redhat packages. (issue 5114)

If the JNLP-connected slave drops out without the master not noticing, allow the reconnection without rejecting it. (issue 5055)

Fixed a trademark bug that caused a considerable fiasco by renaming to Jenkins

Oracle, meanwhile, is continuing to promote Hudson to its userbase, with the Future of Hudson post suggesting the development process is in the process of being worked out:

Our primary goals over the next months will be to fix high-priority bugs in the current edition of Hudson and formalize a development and release process that will allow users of Hudson to have more insight into what is being changed, why it is being changed, and when their bugs will be fixed. We will also continue the discussion that I started last month about what the next version of Hudson (v2) looks like. I look forward to working closely with the community on where to go from here.

Recently, Sonatype came out in support for Hudson:

Very recently, Sonatype completed significant development in the evolution of Hudson’s core architecture. The benefits of these changes include better leveraging of industry standards, increased performance and stability, and tight integration with Maven 3 that provides greater visibility into running builds. We are continuing to add engineers to our Hudson team and are working hard with the Hudson community to move much of the work we've done here to Java.net.

At the moment, the Hudson project and Jenkins project have not yet diverged enough to be significantly different, so there's little to choose between them. However, the success of an open-source project has historically been based on the developer community's activity. And since users tend to follow where projects make progress, commercial tool support for the successful fork often follows.

With Sonatype adding commercial weight to the Hudson developer community, the race to innovate is now on.