How to Install Helix Bugzilla

Contents

How to Install Helix Bugzilla

Helix Bugzilla uses a configuration and installation script, which ensures Helix Bugzilla itself is correctly set up.

System Requirements

Helix Bugzilla is known to work on the following Linux systems:

  • RedHat Enterprise Linux 4
  • CentOS 4.3

In general, Helix Bugzilla will run on any modern Linux system. Helix Bugzilla has not been tested on non-Linux platforms.

Helix Bugzilla requires certain other applications:

  • MySQL v 5.x (http://www.mysql.com/)
  • Apache v 2.x (http://httpd.apache.org/)

Helix Bugzilla also requires several Perl modules. The configuration script will examine the local system and print out the list of missing modules.

Installing Helix Bugzilla from Tarball

  1. Install and configure MySQL and Apache.

  2. Download and unpack the Helix Bugzilla tarball. For example:
cd /var/www
tar -xjf bugzilla-2_17_4-9_1-2.tar.gz
  1. Change to the "bugzilla" directory:
cd bugzilla
  1. Run a check of the system:
./configure check

Correct problems listed during the check (if any), including MySQL permission grants (the script will let you know which permissions to grant).

  1. Perform the actual setup, as root:
./configure setup

Installing From Source

Helix Bugzilla is developed in branches. Periodically, the branches are merged to the HEAD, however the state of the HEAD is not guaranteed, and is not a good location to check out code from.

  1. Install and configure MySQL and Apache.

  2. Check out Helix Bugzilla from a versioned branch, for example:
cd /var/www
cvs -d :ext:user@cvs.helixcommunity.org:/cvsroot/bugzilla co \
  -r bugzilla-2_17_4-9_1-2-branch bugzilla
  1. The remainder of the instructions are the same as installation from a tarball.

Upgrading from Stock Bugzilla

At this time, Helix Bugzilla is not compatible with "stock" (that is, official releases) of Bugzilla itself (from http://www.bugzilla.org/)

Upgrading from Source or Tarball

Bugzilla stores its data in a MySQL database, and some additional data files. Helix Bugzilla has been designed to upgrade itself by first overwriting existing source files, and then re-running the check and setup configuration steps. The configuration process detects that the Bugzilla code has been upgraded, and will properly migrate from the older Bugzilla version to the new version.

Important Note: as with any kind of system upgrade, it is important to back up all data prior to the upgrade, to guard against accidential data loss. While Helix Bugzilla has been tested and used for years within RealNetworks, there is no guarantee that an upgrade won't contain defects which corrupt or delete existing data.

To upgrade from source, simply update the branch in the directory containing Bugzilla:


cd /var/www/bugzilla
cvs -d :ext:user@cvs.helixcommunity.org:/cvsroot/bugzilla update \
  -r bugzilla-2_17_4-9_1-2-branch -dP .

To upgrade from tarball, extract Bugzilla files from the archive, such that the new files overwrite the old files:


cd /var/www
tar -xjf bugzilla-2_17_4-9_1-2.tar.gz

Broken links? Please e-mail: bugzilla-dev@helixcommunity.org
CVS version: $Id: install.html,v 1.9 2007/03/22 18:07:35 damon Exp $