Running the Bitten Slave Locally

The parameter url represents the location of the bitten recipe. If it is a local file, the slave will run the build locally, without any need for a bitten master. This can be useful for trying out bitten-slave quickly. So calling bitten-slave recipe.xml with the following trivial recipe.xml

<build description="Building System"
      xmlns:sh="http://bitten.cmlenz.net/tools/sh">
 <step id="The first step">
   <sh:exec file="echo" args="Minimal example"/>
 </step>
</build>

will produce this output:

[INFO    ] Executing build step 'The first step'
[INFO    ] Minimal example
[INFO    ] Build step The first step completed successfully
[INFO    ] Build completed

Bitten recipes generally specify a list of steps that are required to succeed for a build to be valid. They will often include a list of tests to be ran on the code. Running all the steps can be useful as a pre-commit validation of changes on a development machine, in which case it is important not to delete the files of the working copy, and to build in a specific directory. The command becomes bitten-slave -k -d PATH --build-dir PATH recipe.xml.