comparison doc/install.txt @ 436:cfbc9ee622d5

Finish the move of build configuration management into the admin interface.
author cmlenz
date Fri, 17 Aug 2007 10:43:09 +0000
parents 84b8cde2dfd4
children ad7c5f4b1cf0
comparison
equal deleted inserted replaced
435:8424a8afd1a1 436:cfbc9ee622d5
37 What's left to do now depends on whether you want to use the build master and 37 What's left to do now depends on whether you want to use the build master and
38 web interface, or just the build slave. In the latter case, you're already 38 web interface, or just the build slave. In the latter case, you're already
39 done. You might need to install software that the build of your project 39 done. You might need to install software that the build of your project
40 requires, but the Bitten build slave itself doesn't require anything extra. 40 requires, but the Bitten build slave itself doesn't require anything extra.
41 41
42 For the build master and web interface, you'll need to install Trac 0.10 or 42 For the build master and web interface, you'll need to install Trac_ 0.10 or
43 later. Please refer to the Trac documentation for information on how it is 43 later and the TracWebAdmin_ plugin. Please refer to the Trac documentation for
44 installed. 44 information on how it is installed.
45
46 .. _trac: http://trac.edgewall.org/
47 .. _tracwebadmin: http://trac.edgewall.org/wiki/WebAdmin
45 48
46 49
47 Build Master Configuration 50 Build Master Configuration
48 ========================== 51 ==========================
49 52
51 Bitten to your Trac project environment. If you don't have a Trac project 54 Bitten to your Trac project environment. If you don't have a Trac project
52 set up yet, you'll need to do so in order to use Bitten. 55 set up yet, you'll need to do so in order to use Bitten.
53 56
54 If you already have a Trac project environment, the Bitten plugin needs to be 57 If you already have a Trac project environment, the Bitten plugin needs to be
55 explicitly enabled in the Trac configuration. This is done by adding it to the 58 explicitly enabled in the Trac configuration. This is done by adding it to the
56 [components] section in /path/to/projenv/conf/trac.ini: 59 ``[components]`` section in ``/path/to/projenv/conf/trac.ini``:
57 60
58 .. code-block:: ini 61 .. code-block:: ini
59 62
60 [components] 63 [components]
61 bitten.* = enabled 64 bitten.* = enabled
74 $ trac-admin /path/to/projenv permission add anonymous BUILD_VIEW 77 $ trac-admin /path/to/projenv permission add anonymous BUILD_VIEW
75 $ trac-admin /path/to/projenv permission add [yourname] BUILD_ADMIN 78 $ trac-admin /path/to/projenv permission add [yourname] BUILD_ADMIN
76 79
77 You should now see an additional tab labeled "Build Status" in the Trac 80 You should now see an additional tab labeled "Build Status" in the Trac
78 navigation bar. This link will take you to the list of build configurations, 81 navigation bar. This link will take you to the list of build configurations,
79 which at this point is of course empty. If you've set up permissions 82 which at this point is of course empty.
80 correctly as described previously, you should see a button for adding new 83
81 build configurations. Click that button and fill out the form. Also, add 84 To add build configurations, you need to have the TracWebAdmin_ plugin
82 at least one target platform after saving the configuration. Last but not 85 installed.
83 least, you'll have to "activate" the build configuration. 86
87 .. warning:: The TracWebAdmin needs to be installed even if you're using Trac
88 0.11 or later, which basically provides a builtin web
89 administration interface. Make sure that you disable the plugin in
90 that case, though (``webadmin.* = disabled``). While somewhat
91 counterintuitive, this process allows the Bitten administration UI
92 to neatly integrate into the new web administration interface added
93 in Trac 0.11.
94
95 If both TracWebAdmin_ and Bitten are installed, and you are logged in as a user
96 with the required permissions, you should see additional administration pages
97 inside the “Admin” area, under a group named “Builds”. These pages allow you to
98 set options of the build master, and manage build configurations.
99
100 Add a new build configuration and fill out the form. Also, add at least one
101 target platform after saving the configuration. Last but not least, you'll have
102 to "activate" your new build configuration.
84 103
85 104
86 Running the Build Slave 105 Running the Build Slave
87 ======================= 106 =======================
88 107
Copyright (C) 2012-2017 Edgewall Software