Installing Bugzilla on Microsoft Windows using the Installer
This is an unofficial installer for Bugzilla which deploys and configures Bugzilla with all the prerequisites:
A working SMTP server is required for Bugzilla to send emails.
The current installer does not allow you to use an existing instance of Apache, MySql or Perl. Follow the manual installation instructions should you require this.
You must understand that these installers are provided for testing purposes only and are only available for older versions of Bugzilla. These older versions are vulnerable to several security issues and so shouldn't be used for production. For production, official tarballs are recommended (you have been warned). If you still want to try them, the installers can be downloaded from http://landfill.bugzilla.org/win32installer/.
A Mozilla Community user has created an updated Win32 installer containing Bugzilla 4.2.5 and Testopia 2.5. Please contact him to obtain it: Avinesh Bangar (firstname.lastname@example.org).
Once the installation has completed, a web browser will launch pointing to your Bugzilla install, which will require further configuration. Log in with the Bugzilla account you created and follow the prompts.
The setup creates two Windows Services, "Bugzilla.Apache" and "Bugzilla.MySql". These services can be manually uninstalled or reinstalled using "InstallServices.cmd" and "UninstallServices.cmd" from the "bin" directory.
Running this file (in the installation directory) shows a "Command Prompt" preconfigured to enable you to install perl modules and run Bugzilla scripts (such as checksetup.pl).
Running this file will create a backup of your Bugzilla database in a file "bugzilla-backup.zip".
These packages are no longer supported.
Using this installation for Bugzilla Development
- Read the Bugzilla Developers Guide
- Install the most recent version from landfill
- Download and install Cygwin, make sure you install bzr
- Delete the bugzilla directory from the installed version
- Download SetPaths.cmd and RestoreHashBang.cmd from the source directory on landfill to your installation directory (same level as BugzillaCmdPrompt.cmd)
- Use bzr to checkout trunk or the appropriate branch
- Run SetPaths.cmd to fix the checked out files (do this after every checkout/update)
- To generate a diff, run RestoreHashBang.cmd, generate the diff, then run SetPaths.cmd
- April 13th, 2010 - Bugzilla 3.6 released
- April 8th, 2010 - Fixed issue with upgrade notification mechanism (missing libexpat.dll)
- March 23rd, 2010 - Initial release