Continuous integration tools - JUnit in Action - page 180

Figure 11.5 Hudson initial startup screen

There's also a way to specify different command-line parameters, such as the one to
redefine the port on which the server is started or the root under which the applica-
tion is started.
Also, if you don't want to use the Winstone servlet container, you can use any other
servlet container you want. If you stick with that solution, you'll be forced to follow the
installation procedures specific to the servlet container you use.

11.3.3 Configuring Hudson

Hudson's advantage over CruiseControl is easier configuration, which is done
through the web interface. Once you've installed Hudson, it's time to start the config-
uration. Open a browser and navigate to http://localhost:8888 /. You should see the
Hudson welcome screen, and there should be a Manage Hudson link on the left side.
Click it, and you'll be given a list of additional links leading to the parts of the installa-
tion you want to configure. Click Configure System, and it will open a web page simi-
lar to the one shown in figure 11.6.
As you already saw, Hudson, in contrast to CruiseControl, comes with no Ant
installation, so the tool needs to know where you've installed Ant, Maven, JDK , and
the like. You need to specify this information on the configuration page shown in
figure 11.6.
The first line on the configuration page is Home Directory. The home directory of
Hudson is an interesting creature, so we devote a subsection to it.

H UDSON HOME DIRECTORY
The home directory of Hudson is used to maintain the source, perform builds, and
hold some archives. By default it's located in $ USER_HOME /.hudson ($ USER_HOME
is interpreted as /home/<username> in UNIX systems and as C:\Documents and
Settings\<username>\ in Windows).