View source | Discuss this page | Page history | Printable version   

Continuous Integration Using Hudson


Hudson Intro & Terminology

I am sure most of people would have written at least one cron job, if not please write one ;-) Hudson uses the same scheduling logic, except for polling the SCM for changes.

Like a cron job, hudson also start and stops a job at a specified interval or at every SCM commit. Every job has one or more subtask (ant task in our case). Hudson itself doesn't solve the problem of integration. It shortens the time to find a bug by doing a full or incremental build accordingly. It will also alerts the person who committed the last change set, send a mail to mailing list, irc alert.


We will be using following terminology when we discuss more about hudson. the following bullet points is a cut-copy-paste from Hudson Terminology.

Work Flow

Based on the discussion in the mailing list we have come up with following work flow (Discussion about ci and backout faulty changeset).

  1. Push to main complete blocks of changesets in pi.
    • Means push all the changesets since the last push till the last one that works.
  2. Detect the first changeset not working and reopen the bug which that one is supposed to fix.
  3. Re-fix that bug with that bug with a new changeset, test it and start from step 1.


Setup and Configuration

Installation on Gentoo

Upgrade Hudson

Add Slaves

Environment setup for ERP

Configure jobs

Creating and Configuration of build/job can be done using Hudson web interface.

Process tied with Continuous Integration Hudson


Hudson in your language.

Road Ahead

Challenges and moving ahead !

Retrieved from ""

This page has been accessed 19,897 times. This page was last modified on 13 April 2010, at 11:14. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.