RSS Feed for This PostCurrent Article

Hudson: An Extensible Continuous Integration Engine

I was trying on some of the continuous integration tools like Continuum, CruiseControl, and Hudson. Each one has its own features and after trying them out, I decided to use Hudson. I would like to point out that for those who want to use any continuous integration tool, it is good that you try them out yourself before deciding which one to use.

As quoted from the website, Hudson monitors executions of repeated jobs, such as building a software project or jobs run by cron. Among those things, current Hudson focuses on the following two jobs:

  1. Building/testing software projects continuously, just like CruiseControl or DamageControl. In a nutshell, Hudson provides an easy-to-use so-called continuous integration system, making it easier for developers to integrate changes to the project, and making it easier for users to obtain a fresh build. The automated, continuous build increases the productivity.
  2. Monitoring executions of externally-run jobs, such as cron jobs and procmail jobs, even those that are run on a remote machine. For example, with cron, all you receive is regular e-mails that capture the output, and it is up to you to look at them diligently and notice when it broke. Hudson keeps those outputs and makes it easy for you to notice when something is wrong.

So far I am quite happy using Hudson. It fulfilled all my requirements.


Trackback URL


Sorry, comments for this entry are closed at this time.