Mercurial > bitten > bitten-test
annotate doc/install.txt @ 597:4c3d43adaa48
0.6dev: Fixed `php:phpunit` parsing including support for nested tests. Extended `php:coverage` to also parse PHPUnit coverage-clover format. Closes #199 and #316.
Thanks to all those that have helped develop the patch, and special thanks to Roland Wilczek for contributing, testing and helping me get working php builds for development.
author | osimons |
---|---|
date | Wed, 29 Jul 2009 10:43:48 +0000 |
parents | fe4293ddf51c |
children | 5f3e66e5b451 |
rev | line source |
---|---|
412 | 1 .. -*- mode: rst; encoding: utf-8 -*- |
2 | |
3 ============ | |
4 Installation | |
5 ============ | |
6 | |
7 .. contents:: Contents | |
8 :depth: 2 | |
9 .. sectnum:: | |
10 | |
11 | |
12 Prerequisites | |
13 ============= | |
14 | |
15 Bitten is written in Python, so make sure that you have Python installed. | |
16 You'll need Python 2.3 or later. Also, make sure that setuptools_, version 0.6a2 | |
17 or later, is installed. | |
18 | |
19 .. _setuptools: http://peak.telecommunity.com/DevCenter/setuptools | |
20 | |
21 If that's taken care of, you just need to download and unpack the Bitten | |
22 distribution, and execute the command:: | |
23 | |
24 $ python setup.py install | |
25 | |
26 from the top of the directory where you unpacked (or checked out) the Bitten | |
27 code. Note that you may need administrator/root privileges for this step, as | |
28 it will by default attempt to install Bitten to the Python site-packages | |
29 directory on your system. | |
30 | |
31 It's also a good idea to run the unit tests at this point, to make sure that | |
522
ad7c5f4b1cf0
Added note that you need Trac for the tests; see #265
dfraser
parents:
436
diff
changeset
|
32 the code works as expected on your platform (please note that Trac_ needs to |
ad7c5f4b1cf0
Added note that you need Trac for the tests; see #265
dfraser
parents:
436
diff
changeset
|
33 be installed for the tests to run; see below):: |
412 | 34 |
35 $ python setup.py test | |
36 | |
37 | |
38 What's left to do now depends on whether you want to use the build master and | |
39 web interface, or just the build slave. In the latter case, you're already | |
40 done. You might need to install software that the build of your project | |
41 requires, but the Bitten build slave itself doesn't require anything extra. | |
42 | |
523 | 43 For the build master and web interface, you'll need to install Trac_ 0.11 or |
555
fe4293ddf51c
Removed references to the `TracWebAdmin` plugin which is no longer needed - fixes #387
dfraser
parents:
523
diff
changeset
|
44 later. Please refer to the Trac documentation for information on how it is installed. |
436
cfbc9ee622d5
Finish the move of build configuration management into the admin interface.
cmlenz
parents:
412
diff
changeset
|
45 |
cfbc9ee622d5
Finish the move of build configuration management into the admin interface.
cmlenz
parents:
412
diff
changeset
|
46 .. _trac: http://trac.edgewall.org/ |
412 | 47 |
48 | |
49 Build Master Configuration | |
50 ========================== | |
51 | |
52 Once both Bitten and Trac are installed and working, you'll have to introduce | |
53 Bitten to your Trac project environment. If you don't have a Trac project | |
54 set up yet, you'll need to do so in order to use Bitten. | |
55 | |
56 If you already have a Trac project environment, the Bitten plugin needs to be | |
57 explicitly enabled in the Trac configuration. This is done by adding it to the | |
436
cfbc9ee622d5
Finish the move of build configuration management into the admin interface.
cmlenz
parents:
412
diff
changeset
|
58 ``[components]`` section in ``/path/to/projenv/conf/trac.ini``: |
412 | 59 |
60 .. code-block:: ini | |
61 | |
62 [components] | |
63 bitten.* = enabled | |
64 | |
65 The Trac web interface should now inform you with an error message that the | |
66 environment needs to be upgraded. To do this, run:: | |
67 | |
68 $ trac-admin /path/to/projenv upgrade | |
69 | |
70 This will create the database tables and directories that Bitten requires. | |
71 You probably also want to grant permissions to someone (such as yourself) | |
72 to manage build configurations, and allow anonymous users to view the | |
73 status and results of builds:: | |
74 | |
75 $ trac-admin /path/to/projenv permission add anonymous BUILD_EXEC | |
76 $ trac-admin /path/to/projenv permission add anonymous BUILD_VIEW | |
77 $ trac-admin /path/to/projenv permission add [yourname] BUILD_ADMIN | |
78 | |
79 You should now see an additional tab labeled "Build Status" in the Trac | |
80 navigation bar. This link will take you to the list of build configurations, | |
436
cfbc9ee622d5
Finish the move of build configuration management into the admin interface.
cmlenz
parents:
412
diff
changeset
|
81 which at this point is of course empty. |
cfbc9ee622d5
Finish the move of build configuration management into the admin interface.
cmlenz
parents:
412
diff
changeset
|
82 |
555
fe4293ddf51c
Removed references to the `TracWebAdmin` plugin which is no longer needed - fixes #387
dfraser
parents:
523
diff
changeset
|
83 If Bitten is installed, and you are logged in as a user with the required |
fe4293ddf51c
Removed references to the `TracWebAdmin` plugin which is no longer needed - fixes #387
dfraser
parents:
523
diff
changeset
|
84 permissions, you should see additional administration pages inside the “Admin” |
fe4293ddf51c
Removed references to the `TracWebAdmin` plugin which is no longer needed - fixes #387
dfraser
parents:
523
diff
changeset
|
85 area, under a group named “Builds”. These pages allow you to set options of the |
fe4293ddf51c
Removed references to the `TracWebAdmin` plugin which is no longer needed - fixes #387
dfraser
parents:
523
diff
changeset
|
86 build master, and manage build configurations. |
436
cfbc9ee622d5
Finish the move of build configuration management into the admin interface.
cmlenz
parents:
412
diff
changeset
|
87 |
cfbc9ee622d5
Finish the move of build configuration management into the admin interface.
cmlenz
parents:
412
diff
changeset
|
88 Add a new build configuration and fill out the form. Also, add at least one |
cfbc9ee622d5
Finish the move of build configuration management into the admin interface.
cmlenz
parents:
412
diff
changeset
|
89 target platform after saving the configuration. Last but not least, you'll have |
cfbc9ee622d5
Finish the move of build configuration management into the admin interface.
cmlenz
parents:
412
diff
changeset
|
90 to "activate" your new build configuration. |
412 | 91 |
92 | |
93 Running the Build Slave | |
94 ======================= | |
95 | |
96 The build slave can be run on any machine that can connect to the machine | |
97 on which the build master is running. The installation of Bitten should have put | |
98 a `bitten-slave` executable on your path. If the script is not on your path, | |
99 look for it in the `bin` or `scripts` subdirectory of your Python installation. | |
100 | |
101 To get a list of options for the build slave, execute it with the `--help` | |
102 option:: | |
103 | |
104 $ bitten-slave --help | |
105 | |
106 To run the build slave against a Bitten-enabled Trac site installed at | |
107 http://myproject.example.org/trac, you'd run:: | |
108 | |
109 $ bitten-slave http://myproject.example.org/trac/builds |