Bugzilla.wikimedia.org

From Wikitech
(Difference between revisions)
Jump to: navigation, search
m (Patching Bugzilla)
(Patching Bugzilla: add warning)
Line 89: Line 89:
 
#if the dry run looks fine:
 
#if the dry run looks fine:
 
#patch -p0 < patch.diff  
 
#patch -p0 < patch.diff  
 +
 +
(!)(you may want to create a backup right before applying the patch, or check into -R option to reverse patches if something goes wrong)
  
 
example ticket: [[RT:2061]]
 
example ticket: [[RT:2061]]
  
 
[[Category:Services]]
 
[[Category:Services]]

Revision as of 10:59, 1 December 2011

Our Bugzilla installation is at https://bugzilla.wikimedia.org/, with attachments hosted at http://bug-attachment.wikimedia.org/ . The attachment domain only allows downloading of attachments.

Contents

Hardware

Related services

Software

  • Apache+Perl
  • MySQL
  • Bugzilla
    • With custom templates and tweaks

Upgrade from 3.6.0 to 4.0

Note: This was tested on http://project2.wikimedia.org/bugzilla4 with the following software

  • Ubuntu 8.04.4
  • Mysql 5.0.51a
  • Apache2
  • Perl v5.8.8

Back up the database and the data directory in case anything goes wrong

  • Download and extract Bugzilla 4.0 .
  • Make the following Apache config changes
Apache Config Changes
  • Copy the following from the old Bugzilla installation
localconfig
data/
  • Checkout svn.wikimedia.org/svnroot/mediawiki/trunk/tools/bugzilla/bugzilla-4.0/skins/contrib/Wikimedia into skins/contrib/Wikimedia
  • Checkout svn.wikimedia.org/svnroot/mediawiki/trunk/tools/bugzilla/bugzilla-4.0/template/en/custom into template/en/custom
  • Checkout svn.wikimedia.org/svnroot/mediawiki/trunk/tools/bugzilla/bugzilla-4.0/extensions/Wikimedia into extensions/Wikimedia
  • Checkout svn.wikimedia.org/svnroot/mediawiki/trunk/tools/bugzilla/bugzilla-4.0/extensions/WeeklyReport into extensions/WeeklyReport
    • ln -s extensions/WeeklyReport/component-report.cgi component-report.cgi
    • ln -s extensions/WeeklyReport/weekly-bug-summary.cgi weekly-bug-summary.cgi
  • Run (this is where the database migration will happen so be sure you are ready):
perl checksetup.pl

After this Bugzilla should be up and running with the classic skin

  • Now change the following settings:
    • Administration->Default Preferences->Bugzilla's general appearance (skin) = Wikimedia
    • Administration->Default Preferences->Position of the Additional Comments box = After other comments

REST API

Installation instructions

Setting up Whining

According to the user guide :

For whining to work, a special Perl script must be executed at regular intervals. More information on this is available in Section 2.3.3.

This cron job is currently set up to run once an hour at 15 past the hour. Here's the cron entry:

15 */1 * * * cd <bugzilla-directory> ; ./whine.pl

How to recover in a hurry

Its a good thing we backed up our database and Bugzilla 3.0.8 home directory as part of the upgrade

  • Move the backed up Bugzilla back to its original location
  • Restore the MySQL database from the backup dump
  • Run the checksetup.pl script

Notes

  • Switched to SSL 2008-02

Patches

Patching Bugzilla

Currently patches are still applied manually, but this should be changed soon.

  1. get a .diff file including the patch, for example from hexmode, the bugmeister
  2. scp the file over to "kaulen" and login via ssh
  3. cd to /srv/org/wikimedia/bugzilla and copy the .diff file over here
  4. do a dry run and make sure "-p0" is the right thing (look at file pathes in patch file relative to current dir)
  5. patch --dry-run -p0 < patch.diff
  6. if the dry run looks fine:
  7. patch -p0 < patch.diff

(!)(you may want to create a backup right before applying the patch, or check into -R option to reverse patches if something goes wrong)

example ticket: RT:2061

Personal tools
Namespaces

Variants
Actions
Navigation
Ops documentation
Wiki
Toolbox