Mercurial > bitten > bitten-test
comparison README.txt @ 682:6511c192a957
0.6dev: Complete rework of the slave-only install to use `setuptools.Feature` to disable the master-parts. This should make all regular distribution commands like 'test', 'sdist', 'bdist_egg' and so on work as intended, and the output can be adjusted using option `--without-master` (master is enabled by default).
Also fixes various issues with manifests discovered when making 0.6beta1, leaving these releases somewhat lacking...
Updated docs, readme and changelog.
Hopefully this closes #383 for good... :-)
| author | osimons |
|---|---|
| date | Fri, 11 Sep 2009 20:43:15 +0000 |
| parents | cc1fefd5d814 |
| children |
comparison
equal
deleted
inserted
replaced
| 680:c30ff14dcbd0 | 682:6511c192a957 |
|---|---|
| 41 It's also a good idea to run the unit tests at this point, to make sure that | 41 It's also a good idea to run the unit tests at this point, to make sure that |
| 42 the code works as expected on your platform: | 42 the code works as expected on your platform: |
| 43 | 43 |
| 44 $ python setup.py test | 44 $ python setup.py test |
| 45 | 45 |
| 46 It is also possible to install only the build slave, installing only the | |
| 47 parts of Bitten that are needed by clients to run builds: | |
| 48 | |
| 49 $ python setup.py --without-master install | |
| 46 | 50 |
| 47 What's left to do now depends on whether you want to use the build master and | 51 What's left to do now depends on whether you want to use the build master and |
| 48 web interface, or just the build slave. In the latter case, you're already | 52 web interface, or just the build slave. In the latter case, you're already |
| 49 done. You might need to install software that the build of your project | 53 done. You might need to install software that the build of your project |
| 50 requires, but the Bitten build slave itself doesn't require anything extra. | 54 requires, but the Bitten build slave itself doesn't require anything extra. |