Changes between Version 3 and Version 4 of Bitten Slave Options

Timestamp:

Jun 14, 2008, 9:58:52 PM (16 years ago)

Author:

iain@…

Comment:

Warning not to delete working copies during local builds.

Bitten Slave Options

@@ -47 +47 @@
 
 
-Note that the 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 as a pre-commit check on a development machine, for testing a changed recipe, or just for trying out bitten-slave quickly. So calling {{{bitten-slave recipe.xml}}} with the following trivial recipe.xml
+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
 
 {{{
@@ -66 +66 @@
 [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}}}.