Hudson can be used to perform the typical build server work, such as doing continuous/official/nightly builds, run tests, or perform some repetitive batch tasks. This is called "free-style software project" in Hudson.
Go to Hudson top page, select "New Job", then choose "Build a free-style software project". This job type consists of the following elements:
For more details, click the icons in the configuration page.
There is sometimes a need to build a project simply for demonstration purposes or access to a SVN/CVS repository is unavailable. By choosing to configure the project as "None" under "Source Code Management" you will have to:
When a Hudson job executes, it sets some environment variables that you may use in your shell script, batch command, Ant script or Maven POM 1. The following table contains a list of all of these environment variables.
If you're using a shell script to do your build, you can either put these environment variables directly into your shell scripts, or call them as parameters in your shell script. Below is an example how this can be done:
If you are executing a Windows Batch Command, the variables should be referenced using the %VARIABLE_NAME% pattern. For example:
If you're using an Ant script to do your build, you may include environment variables in property settings. Click on the Advanced... button just below where you put the Ant targets you want to build. This will display the Properties box. Below is an example how to use the Properties box to set Ant properties with Hudson Environment variables:
As an alternative, you can use the Environmental prefix to pull in all environmental variables as properties right inside your build.xml file. Below is an example how to set the property "label" to include the Project Name and the Build Number:
Builds in Hudson can be triggered periodically (on a schedule, specified in configuration), or when source changes in the project have been detected, or they can be automatically triggered by requesting the URL:
This allows you to hook Hudson builds into a variety of setups. For more information (in particular doing this with security enabled), see Remote access API.
To perform builds whenever someone makes a change in the repository, use a post-commit hook (hooks/post-commit for subversion, CVSROOT/loginfo for CVS) to trigger a new build. The hook can use wget/curl to access the build URL shown above, or send email to trigger a build as described below. The trigger may use /polling instead of /build at the end of the URL to make Hudson poll the SCM for changes rather than building immediately. This prevents Hudson from running a build with no relevant changes for commits affecting modules or branches that are unrelated to the job. When using /polling the job must be configured for polling, but the schedule can be empty.
If you have the root account of your system and you are using sendmail, I found it the easiest to tweak /etc/aliases and add the following entry:
and then run "newaliases" command to let sendmail know of the change. Whenever someone sends an e-mail to "hudson-foo@yoursystem", this will trigger a new build. See this for more details about configuring sendmail.
With qmail, you can write /var/qmail/alias/.qmail-hudson as follows: