Hudson (software)

Hudson

Demonstration of Hudson running in browser
Initial release 1.0 7 February 2005 (2005-02-07)[1]
Stable release
3.3.3 / February 15, 2016 (2016-02-15)
Repository git.eclipse.org/c/hudson/org.eclipse.hudson.core.git
Written in Java
Operating system Cross-platform
Type Continuous integration
License Eclipse Public License
Website hudson-ci.org
As of January 15, 2015 (2015-01-15)

Hudson is a continuous integration (CI) tool written in Java, which runs in a servlet container such as Apache Tomcat or the GlassFish application server. It supports SCM tools including CVS, Subversion, Git, Perforce, Clearcase and RTC, and can execute Apache Ant and Apache Maven based projects, as well as arbitrary shell scripts and Windows batch commands. The primary developer of Hudson was Kohsuke Kawaguchi, who worked for Sun Microsystems at the time. Released under the MIT License, Hudson is free software.[2]

Builds can be started by various means, including scheduling via a cron-like mechanism, building when other builds have completed, and by requesting a specific build URL.

Hudson became a popular alternative to CruiseControl and other open-source build servers in 2008.[3][4] At JavaOne conference in May 2008, it was the winner of Duke's Choice Award in the Developer Solutions category.[5]

When Oracle bought Sun, it declared its intention to trademark the Hudson name, and development began on a commercial version. It was decided by the majority of the development community, including Kawaguchi, to continue the project under the name Jenkins in early 2011. Oracle maintained that Hudson was continuing development and that Jenkins was a fork; the Jenkins developers considered Hudson to be the fork.

Interest in Hudson collapsed thereafter. Eventually Oracle donated the remaining Hudson project assets to the Eclipse Foundation at the end of 2012.[6] As of November 2013, there are many more commits per day to the Jenkins project than to Hudson.[7][8][9]

Plugins

Hudson is extensible through a plugin architecture, and many plugins have been made publicly available which extend it far beyond purely being a build tool for Java projects. Plugins are available for integrating Hudson with most version control systems and bug databases. Many build tools are supported via their respective plugins. Plugins can also change the way Hudson looks or add new functionality.

Builds can generate test reports in various formats (JUnit is supported out of the box, others via plugins) and Hudson can display the reports and generate trends and render them in the GUI.

Hudson–Jenkins split

In November 2010, an issue arose in the Hudson community with respect to the infrastructure used, which grew to encompass questions over Oracle's stewardship and perceived control of the project.[10] Negotiations were held between the principal project contributors and Oracle; although there were many areas of agreement, a key sticking point was the control of the name "Hudson" itself, which Oracle claimed, and for which it submitted a trademark registration in early December 2010 (granted on October 25, 2011).[11] As a result, on January 11, 2011, a proposal was made to change the project name from "Hudson" to "Jenkins".[12] The proposal was overwhelmingly approved by those that voted on January 29, 2011, creating the Jenkins project.[13] On February 1, 2011, Oracle indicated that it, in partnership with others in the community, intended to continue development of Hudson.[14]

Move to Eclipse Foundation

On May 3, 2011, the Eclipse Foundation in conjunction with the key Hudson committers, Oracle, Sonatype and other community supporters, put forward a formal proposal for the transfer of Hudson, including the core code and problematic trademarks, to the Eclipse Foundation.[15] Hudson's founder Kohsuke Kawaguchi saw the Oracle move as validating Jenkins. "When we were talking with Oracle to find a middle ground, they made it very clear that they have no intention of giving up the trademark control. But with this move, they clearly acknowledge that Oracle couldn't keep up with the Jenkins project."[16] On January 24, 2012, Eclipse announced the inclusion of Hudson 3 in the Eclipse Foundation.[17]

See also

References

  1. ↑ Kawaguchi, Kohsuke. "Hudson" (PDF). Retrieved 1 July 2015.
  2. ↑ "Hudson Software License". Archived from the original on 2009-02-07.
  3. ↑ Dan Dyer. "Why are you still not using Hudson?". Retrieved 2008-05-21.
  4. ↑ "What is the difference between Hudson and CruiseControl for Java projects?". Stack Overflow. Retrieved 2011-01-17.
  5. ↑ "2008 JavaOne Conference: Duke's Choice Awards Winners for 2008". Retrieved 2008-05-21.
  6. ↑ "Eclipse list of projects".
  7. ↑ Jenkins commit log on Github
  8. ↑ "Jenkins commit log on Github".
  9. ↑ "Hudson commit log on git.eclipse.org".
  10. ↑ "Who's driving this thing?". Retrieved 2011-01-31.
  11. ↑ "Hudson Trademark Listing on Trademarks411". Retrieved 2012-02-13.
  12. ↑ "Hudson's future". Retrieved 2011-01-11.
  13. ↑ "Rename Vote Results". Retrieved 2011-01-29.
  14. ↑ "The Future of Hudson". Retrieved 2011-02-02.
  15. ↑ "Eclipse Foundation proposal". Retrieved 2011-05-03.
  16. ↑ "Oracle hands Hudson to Eclipse, but Jenkins fork seems permanent". InfoWorld. 2011-05-04. Retrieved 2011-08-10.
  17. ↑ "Eclipse Foundation announces Hudson 3.0". Archived from the original on 2013-01-24. Retrieved 2016-02-15.

External links

This article is issued from Wikipedia - version of the 7/25/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.