A part of the configuration of the build will be stored in Jenkins, but it's mostly for publishing the reports and the documentation (if you need it). We saw the actual configuration on how to run the various scripts in Chapter 8, Analyzing Testing Information. This is in the build.xml file. This default name can be picked up by Jenkins automatically. This can be configured, but it's pointless to do so unless you already have a file with that name.

The build file should sit at the root of the project repository, and it should have a valid XML.

The language we are going to use to write the build file is Apache Ant. There are either more complex solutions, such as Maven, or more ad-hoc solutions such as Phing for this, but I still prefer Ant. This is because it's simple and flexible (it's verbose, but once you've written it, there isn't much to be said). It also allows you to run anything that is not specific for a particular language.

We're going to create the...