windows下安装Bugzilla 2.18- -
Tag： Bugzilla
最近刚刚学会了配置Bugzilla，写下自己的过程，希望新人能有帮助：
首先参照Bugzilla官方网站的windows下安装Bugzilla的介绍安装，已经非常的详细，按照这个方法安装很顺利：
http://www.bugzilla.org/docs/win32install.html
Installing Bugzilla From CVS
Download the CVSNT client from http://www.cvsnt.org/ (2.15 Meg).
Run the installation, you'll only need to install the Command line client and the Password Server (:pserver:) Protocol. Once the intsall has completed, log out and log in again to pick up the changes to the PATH.
Note: this document assumes you want to install Bugzilla into C:/Bugzilla.
Open the command line, and cd to the parent of the directory you want to install Bugzilla into. As we'll be installing Bugzilla into C:/Bugzilla, the current directory must be C:/.
C:/>set CVSROOT=:pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot C:/>cvs login Logging in to :pserver:anonymous@cvs-mirror.mozilla.org:2401:/cvsroot CVS password: anonymous C:/>cvs checkout -d Bugzilla -rBUGZILLA-2_18-STABLE Bugzilla cvs checkout: cwd=C:/ ,current=C:/ cvs checkout: Updating Bugzilla U Bugzilla/.cvsignore U Bugzilla/1x1.gif U Bugzilla/Bugzilla.pm U Bugzilla/CGI.pl ... U Bugzilla/template/en/default/search/search-specific.html.tmpl U Bugzilla/template/en/default/search/tabs.html.tmpl cvs checkout: Updating Bugzilla/template/en/default/whine cvs checkout: Updating Bugzilla/template/en/extension cvs checkout: Updating Bugzilla/template/en/extension/hook C:/>
Upgrading From CVS
If you've already installed an earlier version of Bugzilla from CVS or from a TarBall, updating is easy. Even if you've made customisations, CVS is smart enough to merge.
C:/Bugzilla>cvs update -R -d -rBUGZILLA-2_18-STABLE Bugzilla
cvs update: Updating Bugzilla
P Bugzilla/Bug.pm
P Bugzilla/BugMail.pm
P Bugzilla/CGI.pm
P Bugzilla/Chart.pm
P Bugzilla/Config.pm
P Bugzilla/Constants.pm
P Bugzilla/DB.pm
P Bugzilla/Flag.pm
P Bugzilla/Search.pm
P Bugzilla/Series.pm
P Bugzilla/Token.pm
P Bugzilla/User.pm
P Bugzilla/Util.pm
cvs update: Updating Bugzilla/Auth
U Bugzilla/Auth/CGI.pm
cvs update: Updating Bugzilla/Template
cvs update: Updating Bugzilla/Template/Plugin
C:/Bugzilla>
Installing Bugzilla From the TarBall
Download the Bugzilla 2.18 from:
http://bugzilla.org/download.html (1.2 Meg).
Bugzilla ships as a Tarball, which has the extension .tar.gz. Any decent Windows archive tool should be able to extract tarballs.
Extract the archive to the directory of your choice. For the remainder of this document I will assume that you have extracted Bugzilla into C:/Bugzilla.
Upgrading From TarBall
If you installed Bugzilla from the TarBall, the simplest way to upgrade is to follow the CVS Upgrading instructions.
MySQL
Download MySQL 4.1.x and MySQLcc
Download the MySQL "Windows Essentials" installer from:
http://dev.mysql.com/downloads/mysql/4.1.html (14.1 Meg).
MySQL 5.x is still under development and is not recommended.
Download MySQL Control Center (GUI Administration tool) from:
http://dev.mysql.com/downloads/mysqlcc.html (3.4 Meg).
Install
Both MySQL and MySQLcc have a standard Windows installer. It's ok to select a Typical MySQL install (the default). For the remainder of this document I will assume you have installed MySQL into C:/mysql.
Create Bugs Database and User
Use MySQLcc to create the Bugzilla database, and the database user. For the remainder of this document I will assume that both the database and user are named bugs.
Note: when MySQLcc creates a database it will convert any uppercase letters to lowercase, but will display the database in the exact case that you entered. To avoid confusion, use a database name with all lowercase.
Launch MySQLcc and set the host name to localhost. The default MySQL username is root with an empty password. (This default account is accessible only from localhost).
Connect to the server (Action --> Connect), select "Databases" in the left panel, then create a new database (Action --> New Database) called bugs.
Select User Administration and create a new user (Action --> New User). Username should be bugs, host should be localhost, set the password to whatever you want, and ensure you check the bugs database in the "Allow access to" section, and check With GRANT option.
You can also create the database and user manually with mysql.exe ('sockmonkey' is my password for the bugs account):
C:/mysql/bin>mysql --user=root -p mysql Enter password: ******** Welcome to the MySQL monitor. Commands end with ; or /g. Your MySQL connection id is 15 to server version: 4.0.20a-debug Type 'help;' or '/h' for help. Type '/c' to clear the buffer. mysql> create database bugs; Query OK, 1 row affected (0.11 sec) mysql> grant all privileges on bugs.* to 'bugs'@'localhost' identified by 'sockmonkey'; Query OK, 0 rows affected (0.03 sec) mysql> flush privileges; Query OK, 0 rows affected (0.00 sec) mysql> quit Bye C:/mysql/bin>
If you are running MySQL 4.1, you may encounter the Client does not support authentication protocol requested by server error message. To fix this, once the user has been created you will have to reset the password using OLD_PASSWORD:
C:/mysql/bin>mysql --user=root -p mysql Enter password: ******** Welcome to the MySQL monitor. Commands end with ; or /g. Your MySQL connection id is 15 to server version: 4.1.11-nt Type 'help;' or '/h' for help. Type '/c' to clear the buffer. mysql> set password for 'bugs'@'localhost' = OLD_PASSWORD('sockmonkey'); Query OK, 0 rows affected (0.00 sec) mysql> quit Bye C:/mysql/bin>
ActiveState Perl
Download ActiveState Perl 5.8.1 or Higher
Download the ActiveState Perl 5.8.1 or Higher MSI from:
http://activestate.com/Products/Download/Download.plex?id=ActivePerl (12.5 Meg).
Note that Bugzilla requires ActiveState Perl 5.8.1 as it needs CGI.pm version 2.93 or higher. 5.8.0 ships with CGI.pm version 2.81, 5.8.1 ships with CGI.pm version 3.00.
There is a bug in Time::Local 1.10, which is shipped with ActiveState Perl 5.8.6, that will cause warnings to be generated at the top of every buglist. It's a good idea to avoid version 5.8.6 (version 5.8.4 works without issue).
Install
ActiveState Perl uses a standard Windows Installer. Install, sticking with the defaults, which will install Perl into C:/Perl.
Note: Installing Perl into a directory that contains a space (eg "C:/Program Files") will break the Template-Toolkit installer.
Once the intsall has completed, log out and log in again to pick up the changes to the PATH.
Upgrading Existing Installs
If you already have ActiveState Perl installed, now's a good time to ensure you're running the latest version of ActiveState Perl, along with the latest versions of the modules.
To upgrade ActiveState Perl, follow the directions at:
http://aspn.activestate.com/ASPN/docs/ActivePerl/install.html
To upgrade your modules, simply run ppm upgrade
Create Temp Directory
On Windows, Perl has a hard time of locating the correct directory to write its temporary files (CGI.pm, File::Spec). Basically it has a list of paths hard coded to use, instead of querying Windows for the correct path.
To avoid problems, create the C:/Temp directory (it has to be on drive C) and ensure SYSTEM has write and modify access.
Install Modules
Bugzilla requires a number of perl modules to be installed, all of which are available at http://landfill.bugzilla.org/ppm/.
If you use a proxy server or a firewall you may have trouble running PPM. This is covered in the ActivePerl FAQ.
The Net::LDAP module is only required if you want to use Active Directory for authentication.
C:/>ppm PPM - Programmer's Package Manager version 3.1. Copyright (c) 2001 ActiveState Corp. All Rights Reserved. ActiveState is a devision of Sophos. Entering interactive shell. Using Term::ReadLine::Stub as readline library. Type 'help' to get started. ppm> rep add Bugzilla http://landfill.bugzilla.org/ppm Repositories: [1] ActiveState PPM2 Repository [2] ActiveState Package Repository [3] Bugzilla ppm> install AppConfig ==================== Install 'AppConfig' version 1.52 in ActivePerl 5.8.4.810. ==================== Downloaded 50508 bytes. ... Successfully installed AppConfig version 1.52 in ActivePerl 5.8.4.810. ppm> install TimeDate ==================== Install 'TimeDate' version 1.16 in ActivePerl 5.8.4.810. ==================== Downloaded 19235 bytes. ... Successfully installed TimeDate version 1.16 in ActivePerl 5.8.4.810. ppm> install DBI ==================== Install 'DBI' version 1.43 in ActivePerl 5.8.4.810. ==================== Downloaded 508164 bytes. ... Successfully installed DBI version 1.43 in ActivePerl 5.8.4.810. ppm> install DBD-mysql ==================== Install 'DBD-mysql' version 2.9002 in ActivePerl 5.8.4.810. ==================== Downloaded 178803 bytes. ... Successfully installed DBD-mysql version 2.9002 in ActivePerl 5.8.4.810. ppm> install Template-Toolkit ==================== Install 'Template-Toolkit' version 2.13 in ActivePerl 5.8.4.810. ==================== Downloaded 530770 bytes. ... Successfully installed Template-Toolkit version 2.13 in ActivePerl 5.8.4.810. ppm> install GD ==================== Install 'GD' version 2.07 in ActivePerl 5.8.4.810. ==================== Downloaded 363039 bytes. ... Successfully installed GD version 2.07 in ActivePerl 5.8.4.810. ppm> install Chart ==================== Install 'Chart' version 2.3 in ActivePerl 5.8.4.810. ==================== Downloaded 58641 bytes. ... Successfully installed Chart version 2.3 in ActivePerl 5.8.4.810. ppm> install GDGraph ==================== Install 'GDTextUtil' version 0.86 in ActivePerl 5.8.4.810. ==================== Downloaded 19178 bytes. ... Successfully installed GDTextUtil version 0.86 in ActivePerl 5.8.4.810. ==================== Install 'GDGraph' version 1.43 in ActivePerl 5.8.4.810. ==================== Downloaded 71764 bytes. ... Successfully installed GDGraph version 1.43 in ActivePerl 5.8.4.810. ppm> install PatchReader ==================== Install 'PatchReader' version 0.9.4 in ActivePerl 5.8.4.810. ==================== Downloaded 9558 bytes. ... Successfully installed PatchReader version 0.9.4 in ActivePerl 5.8.4.810. ppm> install Net::LDAP ==================== Install 'Convert-ASN1' version 0.19 in ActivePerl 5.8.2.808. ==================== Downloaded 26326 bytes. ... Successfully installed Convert-ASN1 version 0.19 in ActivePerl 5.8.2.808. ==================== Install 'perl-ldap' version 0.33 in ActivePerl 5.8.2.808. ==================== Downloaded 188548 bytes. ... Successfully installed perl-ldap version 0.33 in ActivePerl 5.8.2.808. ==================== Install 'Net-LDAP-Express' version 0.11 in ActivePerl 5.8.2.808. ==================== Downloaded 7693 bytes. ... Successfully installed Net-LDAP-Express version 0.11 in ActivePerl 5.8.2.808. ppm>
PatchReader 0.9.4
Make sure the version of PatchReader that is installed is 0.9.4 or higher. If you end up with an older version, uninstall the ppm and install the ppm from http://landfill.bugzilla.org/ppm/PatchReader.ppd.
ppm> uninstall PatchReader ==================== Remove 'PatchReader' version 0.9.2 from ActivePerl 5.8.4.810. ==================== ... Successfully removed PatchReader version 0.9.2 from ActivePerl 5.8.4.810. ppm> install http://landfill.bugzilla.org/ppm/PatchReader.ppd ==================== Install 'PatchReader' version 0.9.4 in ActivePerl 5.8.4.810. ==================== Downloaded 9558 bytes. ... Successfully installed PatchReader version 0.9.4 in ActivePerl 5.8.4.810. ppm>
Apache
It is recommended that you run Bugzilla with the Apache web server. If you want to use IIS to run Bugzilla, there are configuration instructions in the Bugzilla documentation.
Download Apache 2.x
Download the Apache HTTP Server version 2.x or high from:
http://httpd.apache.org/download.cgi (5.8 Meg).
Install
Yet another standard Windows Installer. Just follow the prompts, making sure you Install for All Users. Be aware the Apache will always install itself into an Apache2 directory under what ever path you specify. The default install path will be displayed as C:/Program Files/Apache Group which will result in Apache being installed to C:/Program Files/Apache Group/Apache2. This gets me every time.
For the remainder of this document I will assume you installed Apache into the default location, C:/Program Files/Apache Group/Apache2.
If you are already running IIS, you must configure apache to run on a port other than 80, however you aren't asked the port to listen on at install time. Choose All Users (which says port 80), and we'll change the port later.
By default Apache installs itself to run as the SYSTEM account. For security reasons it's better the reconfigure the service to run as an Apache user. Create a user that is a member of no groups, and reconfigure the Apache2 service to run as that account.
Grant write access for Apache account
By default Apache will run as the SYSTEM account. This account needs write and modify access to the following directorys, and all their subdirectories. Depending on your version of Windows, this access may already be granted.
- C:/Bugzilla/data
- C:/Program Files/Apache Group/Apache2/logs
- C:/Temp
Note that C:/Bugzilla/data is created the first time you run checksetup.pl.
Configure Port and DocumentRoot
Edit C:/Program Files/Apache Group/Apache2/conf/httpd.conf with your favourite text editor.
To change the port that Apache runs on (listens on, or binds to), edit the Listen option.
#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the
# directive.
#
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
#
#Listen 12.34.56.78:80
Listen 80
Change the DocumentRoot setting to point to C:/Bugzilla. Note there are two locations in httpd.conf that need to be updated. Note you need to use / instead of / as a path separator.
# # DocumentRoot: The directory out of which you will serve your # documents. By default, all requests are taken from this directory, but # symbolic links and aliases may be used to point to other locations. # DocumentRoot "C:/Bugzilla" # # Each directory to which Apache has access can be configured with respect # to which services and features are allowed and/or disabled in that # directory (and its subdirectories). # # First, we configure the "default" to be a very restrictive set of # features. # Options FollowSymLinks AllowOverride None # # Note that from this point forward you must specifically allow # particular features to be enabled - so if something's not working as # you might expect, make sure that you have specifically enabled it # below. # # # This should be changed to whatever you set DocumentRoot to. #
Configure CGI
To enable CGI support in Apache, you need to enable the CGI handler, by uncommenting the AddHandler cgi-script .cgi line.
#
# AddHandler allows you to map certain file extensions to "handlers":
# actions unrelated to filetype. These can be either built into the server
# or added with the Action directive (see below)
#
# To use CGI scripts outside of ScriptAliased directories:
# (You will also need to add "ExecCGI" to the "Options" directive.)
#
AddHandler cgi-script .cgi
And allow .cgi scripts in the Bugzilla directory by adding the ExecCGI option. We also need to allow Bugzilla's .htaccess file to restrict access to sensitive documents by allowing it to override the defaults. This involves changing AllowOverride None to AllowOverride All.
Apache also needs to know to use Perl to execute .cgi files, via the ScriptInterpreterSource directive.
# # This should be changed to whatever you set DocumentRoot to. # # # Possible values for the Options directive are "None", "All", # or any combination of: # Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews # # Note that "MultiViews" must be named *explicitly* --- "Options All" # doesn't give it to you. # # The Options directive is both complicated and important. Please see # http://httpd.apache.org/docs-2.0/mod/core.html#options # for more information. # Options Indexes FollowSymLinks ExecCGI # # AllowOverride controls what directives may be placed in .htaccess files. # It can be "All", "None", or any combination of the keywords: # Options FileInfo AuthConfig Limit # AllowOverride All # # Controls who can get stuff from this server. # Order allow,deny Allow from all # # Tell Apache to use Perl to execute .cgi # ScriptInterpreterSource Registry-Strict
You also should add index.cgi to the DirectoryIndex list.
#
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
#
# The index.html.var file (a type-map) is used to deliver content-
# negotiated documents. The MultiViews Option can be used for the
# same purpose, but it is much slower.
#
DirectoryIndex index.html index.html.var index.cgi
In order for ScriptInterpreterSource Registry-Strict to work, you also need to add an entry to the Registry so Apache will use Perl to execute .cgi files.
Create a key HKEY_CLASSES_ROOT/.cgi/Shell/ExecCGI/Command with the default value of the full path of perl.exe with a -T parameter. For example C:/Perl/bin/perl.exe -T
Disable Logging
Unless you want to keep statistics on how many hits your Bugzilla install is getting, it's a good idea to disable logging by commenting out the CustomLog directive.
#
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a
# container, they will be logged here. Contrariwise, if you *do*
# define per-
access logfiles, transactions will be
# logged therein and *not* in this file.
#
#CustomLog logs/access.log common
Restart Apache
Finally, restart Apache to get it pick up the changes.
C:/>net stop apache2 The Apache2 service is stopping.. The Apache2 service was stopped successfully. C:/>net start apache2 The Apache2 service is starting. The Apache2 service was started successfully. C:/>
Extras
Until Bug 49893 lands, Bugzilla requires SendMail to send emails. There is a SendMail wrapper designed to work with Bugzilla at http://www.glob.com.au/sendmail/. Download and install as per the instructions on that site.
Note that if you enable logging in Sendmail, you need to ensure that your Apache account has write access to C:/usr/lib.
Configure Bugzilla
checksetup.pl
Run checksetup.pl. This will check your Perl modules and create localconfig.
C:/>cd bugzilla C:/bugzilla>perl checksetup.pl Checking perl modules ... Checking for AppConfig (v1.52) ok: found v1.52 Checking for CGI (v2.93) ok: found v3.04 Checking for Data::Dumper (any) ok: found v2.121 Checking for Date::Format (v2.21) ok: found v2.22 Checking for DBI (v1.32) ok: found v1.43 Checking for DBD::mysql (v2.1010) ok: found v2.9002 Checking for File::Spec (v0.82) ok: found v0.87 Checking for File::Temp (any) ok: found v0.14 Checking for Template (v2.08) ok: found v2.13 Checking for Text::Wrap (v2001.0131) ok: found v2001.09291 The following Perl modules are optional: Checking for GD (v1.20) ok: found v2.07 Checking for Chart::Base (v0.99) ok: found v2.3 Checking for XML::Parser (any) ok: found v2.34 Checking for GD::Graph (any) ok: found v1.43 Checking for GD::Text::Align (any) ok: found v1.18 Checking for PatchReader (any) ok: found v0.9.4 Most ActivePerl modules are available at Apache's ppm repository. A list of mirrors is available at http://www.apache.org/dyn/closer.cgi/perl/win32-bin/ppms/ You can add the repository with the following command: ppm rep add apache http://www.apache.org/dist/perl/win32-bin/ppms/ Checking user setup ... This version of Bugzilla contains some variables that you may want to change and adapt to your local settings. Please edit the file './localconfig' and rerun checksetup.pl The following variables are new to localconfig since you last ran checksetup.pl: index_html cvsbin interdiffbin diffpath create_htaccess webserv ergroup db_host db_pass db_sock db_check severities priorities opsys platforms C:/bugzilla>
Edit localconfig
Open C:/Bugzilla/localconfig in your favourite text editor to configure Bugzilla.
You have to tell Bugzilla how to access your database. If you used bugs/bugs, you'll only have to set db_pass.
#
# How to access the SQL database:
#
$db_host = "localhost"; # where is the database?
$db_port = 3306; # which port to use
$db_name = "bugs"; # name of the MySQL database
$db_user = "bugs"; # user to attach to the MySQL database
#
# Enter your database password here. It's normally advisable to specify
# a password for your bugzilla database user.
# If you use apostrophe (') or a backslash (/) in your password, you'll
# need to escape it by preceding it with a / character. (/') or (//)
#
$db_pass = 'sockmonkey';
checksetup.pl
Run checksetup.pl again. This time it will build your database tables and initialise Bugzilla.
C:/bugzilla>perl checksetup.pl
Checking perl modules ...
Checking for AppConfig (v1.52) ok: found v1.52
Checking for CGI (v2.93) ok: found v3.04
Checking for Data::Dumper (any) ok: found v2.121
Checking for Date::Format (v2.21) ok: found v2.22
Checking for DBI (v1.32) ok: found v1.43
Checking for DBD::mysql (v2.1010) ok: found v2.9002
Checking for File::Spec (v0.82) ok: found v0.87
Checking for File::Temp (any) ok: found v0.14
Checking for Template (v2.08) ok: found v2.13
Checking for Text::Wrap (v2001.0131) ok: found v2001.09291
The following Perl modules are optional:
Checking for GD (v1.20) ok: found v2.07
Checking for Chart::Base (v0.99) ok: found v2.3
Checking for XML::Parser (any) ok: found v2.34
Checking for GD::Graph (any) ok: found v1.43
Checking for GD::Text::Align (any) ok: found v1.18
Checking for PatchReader (any) ok: found v0.9.4
Most ActivePerl modules are available at Apache's ppm repository.
A list of mirrors is available at
http://www.apache.org/dyn/closer.cgi/perl/win32-bin/ppms/
You can add the repository with the following command:
ppm rep add apache http://www.apache.org/dist/perl/win32-bin/ppms/
Checking user setup ...
Creating data directory (./data) ...
Creating graphs directory...
Creating .htaccess...
Creating Bugzilla/.htaccess...
Creating ./data/.htaccess...
Creating ./template/.htaccess...
Creating ./data/webdot/.htaccess...
Precompiling templates ...
Checking for MySQL Server (v3.23.41) ok: found v4.0.20a-debug
Creating table user_group_map ...
Creating table series_data ...
Creating table longdescs ...
Creating table dependencies ...
Creating table components ...
Creating table keywords ...
Creating table cc ...
Creating table duplicates ...
Creating table groups ...
Creating table flagtypes ...
Creating table profiles ...
Creating table products ...
Creating table bugs_activity ...
Creating table series_categories ...
Creating table keyworddefs ...
Creating table fielddefs ...
Creating table group_control_map ...
Creating table profiles_activity ...
Creating table group_group_map ...
Creating table user_series_map ...
Creating table bugs ...
Creating table series ...
Creating table versions ...
Creating table flagexclusions ...
Creating table logincookies ...
Creating table watch ...
Creating table bug_group_map ...
Creating table votes ...
Creating table attachments ...
Creating table flags ...
Creating table milestones ...
Creating table tokens ...
Creating table flaginclusions ...
Creating table quips ...
Creating table namedqueries ...
Creating initial dummy product 'TestProduct' ...
Populating duplicates table...
Creating duplicates directory...
Migrating old chart data into database ...
Adding group tweakparams ...
Adding group editusers ...
Adding group creategroups ...
Adding group editcomponents ...
Adding group editkeywords ...
Adding group admin ...
Adding group editbugs ...
Adding group canconfirm ...
Looks like we don't have an administrator set up yet. Either this is your
first time using Bugzilla, or your administrator's privileges might have
accidently been deleted.
Enter the e-mail address of the administrator: byron@example.com
You entered 'byron@example.com'. Is this correct? [Y/n] y
Enter the real name of the administrator: Byron Jones
Enter a password for the administrator account: beef
Please retype the password to verify: beef
'byron@example.com' is now set up as an administrator account.
C:/bugzilla>
Parameters
You should now be able to log into to Bugzilla using the account checksetup.pl just created. Point your web browser to http://localhost/, choose Log in to an existing account, and login.
In the page footer, choose Parameters.
Put in your email address as the maintainer.
Put in the URL to Bugzilla in the urlbase field. This URL will be used in emails, so don't use localhost.
Download and install WebDot from http://www.graphviz.org/Download_windows.php. Put the complete path to dot.exe in webdotbase.
* A complete file path to 'dot' (part of GraphViz) will generate the graphs locally.
* A URL prefix pointing to an installation of the webdot package will generate the graphs remotely.
* A blank value will disable dependency graphing.
The default value is a publically-accessible webdot server. If you change this value, make certain that the webdot server can read files from your webdot directory. On Apache you do this by editing the .htaccess file, for other systems the needed measures may vary. You can run checksetup.pl to recreate the .htaccess file if it has been lost.
Scheduled Tasks
collectstats.pl
Add a Scheduled Task to run collectstats.pl nightly.
Step-by-step for Windows XP:
- Control Panel --> Scheduled Tasks --> Add Scheduled Task
- Next
- Browse
- Find perl.exe (normally C:/Perl/bin/perl.exe)
- Give it a name, such as "Bugzilla Collect Stats"
- Perfom the task daily at your desired time
- If you're running Apache as a user, not as SYSTEM, enter that user here. Otherwise you're best off creating an account that has write access to the Bugzilla directory and using that
- Tick "Open Advanced Properties.." and click Finish
- Append "-T" and the script name to the end of the "Run" field. eg C:/Perl/bin/perl.exe -T C:/Bugzilla/collectstats.pl
- Change "start in" to the Bugzilla directory
whineatnews.pl
Add a Scheduled Task to run whineatnews.pl nightly.
The steps for setting up whineatnews.pl are as per collectstats.pl, however due to Bug 298405 you may get an error stating that collectstats.pl "Can't locate Bugzilla/BugMail.pm". Until this Bug is fixed you'll have to include a -I parameter with a reference to the Bugzilla directory in the "Run" field. eg C:/Perl/bin/perl.exe -T -I C:/Bugzilla C:/Bugzilla/whineatnews.pl
Backing up Bugzilla
You may want to backup the entire Bugzilla directory. It's small and you'll get all your settings and customisations on your backup media.
The most important component of Bugzilla to backup is the Bugzilla Database. It contains all your Bugs, Users, Attachments, pretty well everything. Like most databases, backups with MySql are performed by generating a dump of the database and backing up the dump.
Schedule the mysqldump utility to create the dump, and add the resulting file to your backup media. You'll find MySql's mysqldump documentation at http://dev.mysql.com/doc/mysql/en/mysqldump.html.
Congratulations, the Bugzilla installation process is complete!
配置过程写的非常好，我是第一次接触就已经配置成功了，所以专门列了出来，由于我是完全按照上面的方法配置的，其中创建数据库的时候管理员mail我录入的是like@example.com,事后也不知道怎么改，所以要谨慎，管理员的mail一定要是一个可以使用的地址，免得事后不好修改。当我配置好了以后发现存在一些问题,其中最大的问题就是bugzilla的邮件系统，用sendmail根本没有办法工作。于是我下载了winwebmail做了一个邮件服务器，效果不错，但是我不会配置bugzilla怎么使用这个邮件服务器，第一次接触什么的都不懂啊，于是网上搜索了好多文章看，其中：
双子的天空 的 windows下Bugzilla 2.18版安装调试心得：
http://magicjl.blogdriver.com/magicjl/519994.html
猪头小队长 的 让bugzilla离开sendmail!
http://www.simplelife.cn/blog/index.php?op=ViewArticle&articleId=65&blogId=1
让我学会了怎么修改，我自己的修改是：
修改Bugzilla/Bugzilla/BugMail.pm里面的最后一个函数sub MessageToMTA ($;$)
修改前为：
sub MessageToMTA ($;$) {
my ($msg, $rcpt_to) = (@_);
my $sendmailparam = "";
unless (Param("sendmailnow")) {
$sendmailparam = "-ODeliveryMode=deferred";
}
if ($enableSendMail == 1) {
open(SENDMAIL, "|/usr/lib/sendmail $sendmailparam -t -i") ||
die "Can't open sendmail";
print SENDMAIL trim($msg) . "/n";
close SENDMAIL;
}
}
修改后为：
sub MessageToMTA ($;$) {
my ($msg, $rcpt_to) = (@_);
my $sendmailparam = "";
unless (Param("sendmailnow")) {
$sendmailparam = "-ODeliveryMode=deferred";
}
if ($enableSendMail == 1) {
#open(SENDMAIL, "|/usr/lib/sendmail $sendmailparam -t -i") ||
# die "Can't open sendmail";
#print SENDMAIL trim($msg) . "/n";
#close SENDMAIL;
use Net::SMTP;
my $smtp_server = '127.0.0.1';
my $smtp_user = 'like@like.com';
my $smtp_pass = 'like';
my $smtp = Net::SMTP->new($smtp_server) ||
die 'Cannot connect to server /'$smtp_server/'';
$smtp->auth($smtp_user,$smtp_pass);
$smtp->mail($smtp_user);
$smtp->to($rcpt_to);
$smtp->data();
$smtp->datasend($msg);
$smtp->dataend();
$smtp->quit;
}
}
我是在自己机器上建立的一个邮件服务器，所以stmp-server是127.0.0.1，like@like.com就是一个账号，like是密码。设置好以后就可以用了，我的目的是在局域网内使用，所以用那个邮件服务器创建的账号，之后就可以使用了。
同时我还下载了bugzilla2.18.3汉化包，但是存在问题，当提交一个bug的时候会出错，具体没有看怎么回事，大家可以试试看。
扫一扫
5814
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
