1 |
Bugzilla is a powerful bug tracking system used by a large number of open |
2 |
source projects. |
3 |
|
4 |
In order to use Bugzilla, you will first need to configure it for your |
5 |
environment. The first step to doing this is to run the checksetup.pl |
6 |
script, which will perform module version checks and create an initial |
7 |
config file in /etc/bugzilla called localconfig. You then need to ensure |
8 |
the values in this file are accurate for your environment. |
9 |
|
10 |
Once this is done, you may need to modify default settings for your database |
11 |
to ensure it accepts Bugzilla data properly. Please see |
12 |
https://bugzilla.readthedocs.org/en/5.0/ for specifics of |
13 |
database setting modifications. |
14 |
|
15 |
Lastly, simply re-run checksetup.pl to populate the database tables, set up |
16 |
the templates, and add the administrator ID. You should be done at this point. |
17 |
|
18 |
There are two useful cron jobs which are included with Bugzilla which should be |
19 |
put in place after configuration is done. The first is a daily cron job for |
20 |
statistics collection. This is in the file "cron.daily" and can be enabled by |
21 |
simply copying this file to /etc/cron.daily/bugzilla (or any other file name |
22 |
in the /etc/cron.daily/ directory). The second is the "whine" cron job, |
23 |
designed to run every 15 minutes. To enable this job, simply copy the |
24 |
cron.whine file to /etc/cron.d/bugzilla (or any othe filename within the |
25 |
/etc/cron.d/ directory). |