Link Details

Hudson 3.0 introduces important new functionality and simpler installation and administration for developers. Hudson 3.0 highlights: Plug-In Manager: Simplifies management and installation from a repository of over 400 existing plug-ins. It also enables the registration of custom plug-in repositories. Additional administrative settings give IT control over the range of plugins available to Hudson administrators. Simplified installation: New self-installation and Bootstrap configuration enables configuration during first launch and just-in-time loading of non-Eclipse components. Architectural improvements and abstraction layer: Hudson core scripting and charting layers have been abstracted to support different technologies such as Eclipse BIRT for charts. Smaller footprint and Eclipse compliance: The size of Hudson footprint has been reduced by 50 percent. This was the result of the work to modernize and change the underlying libraries used in Hudson to meet Eclipse IP requirements. Libraries using GPL or LGPL licenses were removed, existing libraries were updated to the latest versions, and library redundancies were resolved. Support and certification for top plug-ins: Ensures that the most frequently used Hudson plug-ins can integrate with the latest versions. Improved look and feel: Web interface redesign using JQuery provides a more responsive user interface. [ ] References: http://eclipse.org/hudson/changelog.php http://eclipse.org/hudson/

Posted by dev.stonez  |   Jan 30 2013 / 22:45

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Comments

User 226303 avatar

devdanke replied ago:

It appears that both Hudson and Jenkins are adding useful new features and becoming more robust. The Oracle debacle indirectly triggered these improvements and directly caused the Hudson->Jenkins fork. So, at least one good thing came from Oracle's ineptitude. Now that Hudson and Jenkins are safe from Oracle, there's no good reason why developers should have to choose one over the other. Instead, it's time to start thinking about how to merge these projects back together, so all developers can benefit from the improvements in both. Who will take up this noble quest? Or has it already begun?

Reply 0 votes

Recommended Links

Scala
Written by: Ryan Knight
Featured Refcardz: Top Refcardz:
  1. Apache Hadoop
  2. Play
  3. Akka
  4. Debugging JavaScript
  5. Design Patterns
  1. Apache Hadoop
  2. REST
  3. Java
  4. Git
  5. Java Performance
Connect with DZone