Diff for "Bugs/BugzillaPlugin"

Not logged in - Log In / Register

Differences between revisions 4 and 5
Revision 4 as of 2008-08-20 10:56:36
Size: 3423
Editor: 92-237-59-186
Comment: Header and footer
Revision 5 as of 2008-08-20 11:47:33
Size: 4459
Editor: 92-237-59-186
Comment: Brought into help wiki style and clarified some information
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
= Installing the Launchpad plugin for Bugzilla = = Overview =
Line 5: Line 5:
The [[http://launchpad.net/bugzilla-launchpad|bugzilla-launchpad]] project is a Bugzilla extension that allows Bugzilla and Launchpad to interact. Launchpad can communicate directly with bug trackers that use Bugzilla through the [[http://launchpad.net/bugzilla-launchpad|bugzilla-launchpad]] plugin.
Line 7: Line 7:
If you run a Bugzilla instance, you can use the plugin to:

 * share comment histories between bugs that are tracked both in your Bugzilla tracker and also in Launchpad
 * reduce the server load of bug watches from Launchpad.

To start using the plugin, you need to install it in your Bugzilla environment and also tell Launchpad that you're now using the plugin.
Line 9: Line 15:
== A note on version numbering ==
== Version numbers ==
Line 21: Line 28:
So, a plugin instance with a version number of `0.9-3.2` means that the plugin is version 0.9, compatible with Bugzilla version 3.2. So, a plugin instance with a version number of `0.9-3.2` means that this is version 0.9 of the plugin and it is compatible with Bugzilla version 3.2.
Line 23: Line 30:
= Getting the plugin =
Line 24: Line 32:
== Getting the plugin == You can download the plugin from its [[https://launchpad.net/bugzilla-launchpad/+download|Launchpad project page]]. Make sure you get the right plugin [[#versioning|for your version]] of Bugzilla.
Line 26: Line 34:
You can download the plugin from it's [[https://edge.launchpad.net/bugzilla-launchpad/+download|Launchpad project page]]. Make sure you get the right plugin [[#versioning|for your version]] of Bugzilla.


== Installation ==
= Installation =
Line 33: Line 38:
1. Untar the package: '''Step 1:''' Untar the package:
Line 39: Line 44:
2. Change to your Bugzilla directory: '''Step 2:''' Change to your Bugzilla directory:
Line 45: Line 50:
(That's probably /var/www/html/bugzilla if you followed the standard Bugzilla installation instructions.) '''Tip:''' That's probably /var/www/html/bugzilla if you followed the standard Bugzilla installation instructions.
Line 47: Line 52:
2. Apply the patch to your Bugzilla installation: '''Step 3:''' Apply the patch to your Bugzilla installation:
Line 61: Line 66:
3. Install the extension: '''Step 4:''' Install the extension:
Line 67: Line 72:
4. Run checksetup.pl to install the plugin: '''Step 5:''' Run checksetup.pl to install the plugin:
Line 73: Line 78:
5. checksetup.pl will direct you to a URL to finish the installation. '''Step 6:''' checksetup.pl will direct you to a URL to finish the installation.
Line 77: Line 82:
= Getting Launchpad to work with your bugtracker =
Line 78: Line 84:
== Getting Launchpad to work with your bugtracker == Once the plugin is installed and working you need to register your bugtracker with Launchpad, if it isn't already registered.
Line 80: Line 86:
Once the plugin is installed and working you need to register your bugtracker with Launchpad if it isn't already registered. This is really simple to do: This is really simple to do:
Line 82: Line 88:
 1. Go to http://launchpad.net/bugs/bugtrackers
 2. Check to see if your bugtracker is registered. If it isn't, click the "Register another bugtracker" link at the bottom of the page.
 3. Enter your bugtracker's details and click the "Add" button.
 4. Your bug tracker should now show up in the list of registered bugtrackers (http://launchpad.net/bugs/bugtrackers).
 5. If there are bugs in Launchpad that can be linked to your bug tracker, link them!
 6. If there aren't any bugs in Launchpad you can go to http://staging.launchpad.net and file some test bugs which you can then link to your bugtracker. Remember that staging's database is reset every day, so don't forget to email the Launchpad team at feedback@launchpad.net and let them know that you've filed some bugs for testing. They can then run the bug watch checker against your bug tracker. <<BR>>'''Note''': You may have to wait a day or so for your bugtracker to show up on staging. Alternatively, you can set it up manually by following steps 1-4 but substitute http://staging.launchpad.net for http://launchpad.net where appropriate.
'''Step 1:''' Visit https://launchpad.net/bugs/bugtrackers

'''Step 2:''' Check to see if your bugtracker is registered. If it isn't, click the [[https://edge.launchpad.net/bugs/bugtrackers/+newbugtracker|Register another bugtracker]] link at the bottom of the page.

'''Step 3:''' Enter your bugtracker's details and click the ```Add``` button.

'''Step 4:''' Your bug tracker should now show up in the list of [[http://launchpad.net/bugs/bugtrackers|registered bugtrackers]].

'''Step 5:''' Look through Launchpad to find bugs that are being tracked in Launchpad that are also tracked in your instance of Bugzilla and then link the Launchpad bug reports to your reports in Bugzilla. For example: if there's an Ubuntu package of your software, look to see if there are any bugs filed against that package that you're also tracking upstream.

== What to do if you can't find suitable bugs in Launchpad ==

If you can't see any suitable bugs already in Launchpad, you can create some test bugs in Launchpad's [[https://staging.launchpad.net|staging environment]].

'''Note:''' The database for staging is reset every day with a fresh copy of Launchpad's live production database. This can have two impacts:

 * your test bugs will disappear from staging within the next 24 hours
 * if you've added your bug tracker to Launchpad's production environment in the past 24 hours, you need to add it manually to staging.

= Next steps =

Once you've installed the plugin, [[https://answers.edge.launchpad.net/malone|file a question using Launchpad Answers]] to let the Launchapd team know that you're running the plugin. This will allow the Launchpad Bugs developers and sys admins to finish the setup from their end.

Launchpad Help > Bugs > Launchpad<->Bugzilla plugin

Overview

Launchpad can communicate directly with bug trackers that use Bugzilla through the bugzilla-launchpad plugin.

If you run a Bugzilla instance, you can use the plugin to:

  • share comment histories between bugs that are tracked both in your Bugzilla tracker and also in Launchpad
  • reduce the server load of bug watches from Launchpad.

To start using the plugin, you need to install it in your Bugzilla environment and also tell Launchpad that you're now using the plugin.

Version numbers

The version number of the plugin shows two things:

<plugin version>-<bugzilla version>

<plugin version> is the version of the plugin.

<bugzilla version> is the version of Bugzilla that the plugin is compatible with.

So, a plugin instance with a version number of 0.9-3.2 means that this is version 0.9 of the plugin and it is compatible with Bugzilla version 3.2.

Getting the plugin

You can download the plugin from its Launchpad project page. Make sure you get the right plugin for your version of Bugzilla.

Installation

(Wherever it says <version> in these instructions, we mean "the plugin version number goes here".)

Step 1: Untar the package:

  tar -xzf bugzilla-launchpad-<version>.tar.gz

Step 2: Change to your Bugzilla directory:

  cd /path/to/bugzilla

Tip: That's probably /var/www/html/bugzilla if you followed the standard Bugzilla installation instructions.

Step 3: Apply the patch to your Bugzilla installation:

  patch -p0 -i /path/to/bugzilla-launchpad-<version>/patch.diff

Don't worry, the patch was written and reviewed by the Bugzilla developers themselves, so it's safe to apply.

If you're running Red Hat or an older Fedora, you might have to fix the SELinux permissions on the files after applying the patch:

  /sbin/restorecon -Rv ./

Step 4: Install the extension:

  mv /path/to/bugzilla-launchpad-<version>/launchpad extensions/

Step 5: Run checksetup.pl to install the plugin:

  ./checksetup.pl

Step 6: checksetup.pl will direct you to a URL to finish the installation.

And now the plugin should be working!

Getting Launchpad to work with your bugtracker

Once the plugin is installed and working you need to register your bugtracker with Launchpad, if it isn't already registered.

This is really simple to do:

Step 1: Visit https://launchpad.net/bugs/bugtrackers

Step 2: Check to see if your bugtracker is registered. If it isn't, click the Register another bugtracker link at the bottom of the page.

Step 3: Enter your bugtracker's details and click the Add button.

Step 4: Your bug tracker should now show up in the list of registered bugtrackers.

Step 5: Look through Launchpad to find bugs that are being tracked in Launchpad that are also tracked in your instance of Bugzilla and then link the Launchpad bug reports to your reports in Bugzilla. For example: if there's an Ubuntu package of your software, look to see if there are any bugs filed against that package that you're also tracking upstream.

What to do if you can't find suitable bugs in Launchpad

If you can't see any suitable bugs already in Launchpad, you can create some test bugs in Launchpad's staging environment.

Note: The database for staging is reset every day with a fresh copy of Launchpad's live production database. This can have two impacts:

  • your test bugs will disappear from staging within the next 24 hours
  • if you've added your bug tracker to Launchpad's production environment in the past 24 hours, you need to add it manually to staging.

Next steps

Once you've installed the plugin, file a question using Launchpad Answers to let the Launchapd team know that you're running the plugin. This will allow the Launchpad Bugs developers and sys admins to finish the setup from their end.

< Bug tracker

Bugs/BugzillaPlugin (last edited 2010-11-11 19:43:45 by 122-63-10-108)