Changes between Version 1 and Version 2 of Bitten Run Slave Locally
- Timestamp:
- Jun 20, 2008, 4:46:43 AM (16 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Bitten Run Slave Locally
v1 v2 1 == Running the Bitten Slave Locally == 1 2 2 3 == Running the Bitten Slave Locally == 3 Running the build recipe locally is a useful pre-commit validation of changes on a development machine. In that case it is important not to delete the files of the working copy, and to build in a specific directory, so that the recipe can be run without doing a full checkout. The command becomes 4 {{{ 5 bitten-slave -k -d PATH --build-dir PATH recipe.xml 6 }}} 4 7 5 8 … … 10 13 xmlns:sh="http://bitten.cmlenz.net/tools/sh"> 11 14 <step id="The first step"> 12 <sh:exec file="echo" args=" Minimal example"/>15 <sh:exec file="echo" args="Hello World"/> 13 16 </step> 14 17 </build> … … 19 22 {{{ 20 23 [INFO ] Executing build step 'The first step' 21 [INFO ] Minimal example24 [INFO ] Hello World 22 25 [INFO ] Build step The first step completed successfully 23 26 [INFO ] Build completed 24 27 }}} 25 28 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}}}.
