| 44 | | |
| 45 | | |
| 46 | | == Local Builds == |
| 47 | | |
| 48 | | |
| 49 | | 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 |
| 50 | | |
| 51 | | {{{ |
| 52 | | <build description="Building System" |
| 53 | | xmlns:sh="http://bitten.cmlenz.net/tools/sh"> |
| 54 | | <step id="The first step"> |
| 55 | | <sh:exec file="echo" args="Minimal example"/> |
| 56 | | </step> |
| 57 | | </build> |
| 58 | | }}} |
| 59 | | |
| 60 | | will produce this output: |
| 61 | | |
| 62 | | {{{ |
| 63 | | [INFO ] Executing build step 'The first step' |
| 64 | | [INFO ] Minimal example |
| 65 | | [INFO ] Build step The first step completed successfully |
| 66 | | [INFO ] Build completed |
| 67 | | }}} |
| 68 | | |
| 69 | | 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}}}. |
