Mercurial > bitten > bitten-test
comparison README.txt @ 393:e3ab7698dae7
Updates to the docs.
| author | cmlenz |
|---|---|
| date | Fri, 03 Aug 2007 08:54:56 +0000 |
| parents | 05c684ceb8c6 |
| children | 7f181708d048 |
comparison
equal
deleted
inserted
replaced
| 392:026d9aa41b85 | 393:e3ab7698dae7 |
|---|---|
| 80 This will create the database tables and directories that Bitten requires. | 80 This will create the database tables and directories that Bitten requires. |
| 81 You probably also want to grant permissions to someone (such as yourself) | 81 You probably also want to grant permissions to someone (such as yourself) |
| 82 to manage build configurations, and allow anonymous users to view the | 82 to manage build configurations, and allow anonymous users to view the |
| 83 status and results of builds: | 83 status and results of builds: |
| 84 | 84 |
| 85 $ trac-admin /path/to/projenv permission add anonymous BUILD_EXEC | |
| 85 $ trac-admin /path/to/projenv permission add anonymous BUILD_VIEW | 86 $ trac-admin /path/to/projenv permission add anonymous BUILD_VIEW |
| 86 $ trac-admin /path/to/projenv permission add [yourname] BUILD_ADMIN | 87 $ trac-admin /path/to/projenv permission add [yourname] BUILD_ADMIN |
| 87 | 88 |
| 88 You should now see an additional tab labeled "Build Status" in the Trac | 89 You should now see an additional tab labeled "Build Status" in the Trac |
| 89 navigation bar. This link will take you to the list of build configurations, | 90 navigation bar. This link will take you to the list of build configurations, |
| 115 | 116 |
| 116 Running the Build Slave | 117 Running the Build Slave |
| 117 ----------------------- | 118 ----------------------- |
| 118 | 119 |
| 119 The build slave can be run on any machine that can connect to the machine | 120 The build slave can be run on any machine that can connect to the machine |
| 120 on which the build master is running. Just as with the build master, you | 121 on which the build master is running. The installation of Bitten should have put |
| 121 should find the build slave executable on your path after the installation. | 122 a `bitten-slave` executable on your path. If the script is not on your path, |
| 122 The executable file is called `bitten-slave`. | 123 look for it in the `bin` or `scripts` subdirectory of your Python installation. |
| 123 | 124 |
| 124 To get a list of options for the build slave, execute it with the `--help` | 125 To get a list of options for the build slave, execute it with the `--help` |
| 125 option: | 126 option: |
| 126 | 127 |
| 127 $ bitten-slave --help | 128 $ bitten-slave --help |
| 128 | 129 |
| 129 To run the build slave against a master installed on myproject.example.org, | 130 To run the build slave against a Bitten-enabled Trac site installed at |
| 130 you'd run: | 131 http://myproject.example.org/trac, you'd run: |
| 131 | 132 |
| 132 $ bitten-slave myproject.example.org | 133 $ bitten-slave http://myproject.example.org/trac/builds |
| 133 | 134 |
| 134 | 135 |
| 135 More Information | 136 More Information |
| 136 ---------------- | 137 ---------------- |
| 137 | 138 |