Java Reference
In-Depth Information
field. You can learn more about the cron syntax if you click the corresponding ques-
tion mark next to the trigger.
The next section deals with invoking the build itself. You can specify to execute a
shell script, a Windows batch file, an Ant build file, or a Maven build file. On any of
these you can specify any parameters, targets, goals, and so on. You can also arrange
multiple build steps, such as first invoking a shell script and then running Ant. There's
also the option to rearrange all these steps by dragging and dropping.
The last section configures the post-build triggers. The options listed there will
help you publish the artifact, publish the Javadoc, build some other project, send an
email with the build results, or anything else you need. There's also the option to
select multiple triggers.
After doing all this, you should save the job configuration. This will lead you to the
project's home page (shown in figure 11.8).
From the job's home page you can keep track of the current job. From the menu
on the left side, you can choose to see the changes someone has made on the job,
inspect the workspace of the job, delete the project, configure it, or schedule another
build. You can also subscribe to the build results RSS feeds.
We don't want to wait another hour for the build to be triggered, so let's execute
it right now. On the job's home page, click the Build Now link and wait for the build
to finish.
Now you can see the results of the build execution on the job's home page. You
can see not only when the last build was run, but also when the last successful build
happened. Clicking any build number lets you explore the build itself: which mod-
ules were built, which tests failed or succeeded, and, most important, why (see fig-
ure 11.9).
Once you spend some time using Hudson, you'll probably find it a lot easier to
use. Its entire configuration is done through a nice web interface, and it's relatively
Figure 11.8
Hudson job home page
 
 
Search WWH ::




Custom Search