| 1 | |
| 2 | |
| 3 | == Running the Bitten Slave Locally == |
| 4 | |
| 5 | |
| 6 | 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 |
| 7 | |
| 8 | {{{ |
| 9 | <build description="Building System" |
| 10 | xmlns:sh="http://bitten.cmlenz.net/tools/sh"> |
| 11 | <step id="The first step"> |
| 12 | <sh:exec file="echo" args="Minimal example"/> |
| 13 | </step> |
| 14 | </build> |
| 15 | }}} |
| 16 | |
| 17 | will produce this output: |
| 18 | |
| 19 | {{{ |
| 20 | [INFO ] Executing build step 'The first step' |
| 21 | [INFO ] Minimal example |
| 22 | [INFO ] Build step The first step completed successfully |
| 23 | [INFO ] Build completed |
| 24 | }}} |
| 25 | |
| 26 | 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}}}. |