Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
en:cookbook:buildbot [2010/02/18 17:52] jozee |
en:cookbook:buildbot [2010/08/18 16:47] linea |
||
|---|---|---|---|
| Line 15: | Line 15: | ||
| ===== Commands ===== | ===== Commands ===== | ||
| - | Tazbb can be installed on your machine and run manually from the command line - just type 'tazbb usage' for a list of available functions. Tazbb can be run in report mode and made to display more information with the <nowiki>//'--verbose'//</nowiki> option. | + | Tazbb can be installed on your machine and run manually from the command line - just type 'tazbb usage' for a list of available functions. Tazbb can be run in report mode and made to display more information with the //<nowiki>'--verbose'</nowiki>// option. |
| - | Hg and chroot Wok | + | |
| + | ===== Hg and chroot Wok ===== | ||
| Tazbb uses 2 woks: a clean Hg wok and a wok to build packages in a chroot environment. Each time Tazbb is called; the Hg wok is updated and copied to the build wok, so we avoid messing with build results and can also manually modify receipts or patches directly without affecting the main Hg. If configured correctly 'tazdev update-wok' can also update the Hg wok and copy files. | Tazbb uses 2 woks: a clean Hg wok and a wok to build packages in a chroot environment. Each time Tazbb is called; the Hg wok is updated and copied to the build wok, so we avoid messing with build results and can also manually modify receipts or patches directly without affecting the main Hg. If configured correctly 'tazdev update-wok' can also update the Hg wok and copy files. | ||
| - | Log files | ||
| - | Tazbb uses existing tools such as tazwok to build packages, but generates its own log files and has its own database stored in a text file. The log files are available through the web interface and the default path for the files is: /var/log/tazbb | + | ===== Log files ===== |
| - | Web interface | + | |
| + | Tazbb uses existing tools such as tazwok to build packages, but generates its own log files and has its own database stored in a text file. The log files are available through the web interface and the default path for the files is: ///var/log/tazbb// | ||
| + | |||
| + | ===== Web interface ===== | ||
| - | Tazbb logs all its activity to log files and a cooklist. This information can be displayed through a nice web interface so developers can have a quick overview of the last build results. The Tazbb package provides a PHP web interface, CSS stylesheets and images installed by default in /var/lib/tazbb/web. A symlink is created in /var/www/vhosts by a package, it provides easy access to the generated log files through a virtual host or you can use: http://localhost/vhosts/bb | + | Tazbb logs all its activity to log files and a cooklist. This information can be displayed through a nice web interface so developers can have a quick overview of the last build results. The Tazbb package provides a PHP web interface, CSS stylesheets and images installed by default in ///var/lib/tazbb/web//. A symlink is created in ///var/www/vhosts// by a package, it provides easy access to the generated log files through a virtual host or you can use: http://localhost/vhosts/bb |
| ===== Hg hook ===== | ===== Hg hook ===== | ||
| Line 30: | Line 33: | ||
| Mercurial offers a powerful mechanism to perform automated actions in response to events that occur in a repository. The name Mercurial uses for one of these actions is a hook. So Tazbb can be run each time a commit is done in the wok through a simple hook in the .hgrc file of the repository. Example: | Mercurial offers a powerful mechanism to perform automated actions in response to events that occur in a repository. The name Mercurial uses for one of these actions is a hook. So Tazbb can be run each time a commit is done in the wok through a simple hook in the .hgrc file of the repository. Example: | ||
| - | <code> | + | <file> |
| [hooks] | [hooks] | ||
| commit = tazbb cook-commit | commit = tazbb cook-commit | ||
| - | </code> | + | </file> |
| ===== Cron Job ===== | ===== Cron Job ===== | ||
| - | Tazbb can also be run by a cron tab, so each new commit in the wok will cook the correct package each time you want. Cron can also be used to refresh the report or run a full cook. If the last cook is not yet finished or if tazbb has been run by hand (and is still running), it will exit due to a lock file in ///var/lock//. Example of a cron job to 'tazbb cook commit' every 2 hours and cook all missing, modified or unbuilt packages each night: | + | Tazbb can also be run by a cron tab, so each new commit in the wok will cook the correct package any time you want. Cron can also be used to refresh the report or run a full cook. If the last cook is not yet finished or if tazbb has been run by hand (and is still running), it will exit due to a lock file in ///var/lock//. Example of a cron job to 'tazbb cook commit' every 2 hours and cook all missing, modified or unbuilt packages each night: |
| - | <code> | + | <file> |
| */2 * * * * /usr/bin/tazbb cook-commit | */2 * * * * /usr/bin/tazbb cook-commit | ||
| 03 02 * * * /usr/bin/tazbb cook-all | 03 02 * * * /usr/bin/tazbb cook-all | ||
| - | </code> | + | </file> |
| ===== Database Files ===== | ===== Database Files ===== | ||