Bug tracker import code/adding a bug tracker (moved): Difference between revisions

From OpenHatch wiki
Content added Content deleted
(Created page with '== About this page == There are other pages about our bug tracker import code. == Step by step == === Clone the repository === You will need to have a local copy of our g…')
 
Line 22: Line 22:


Each file has two parts...
Each file has two parts...

* '''One simple bit of code per project bug tracker we download data from''': This is what you want. It's usually toward the end of the file. This is usually a five-line Python class.
* '''The raw code that goes out to the network and fetches data''': This is probably not what you want.

To add a new bug tracker, take an existing bug tracker's short code snippet and copy-paste it, adjusting what you need to adjust. You'll definitely need to change the project name, and you'll probably need to provide URLs for fetching a list of bugs to import.


=== Submit a patch ===
=== Submit a patch ===

Revision as of 15:23, 26 August 2010

About this page

There are other pages about our bug tracker import code.

Step by step

Clone the repository

You will need to have a local copy of our git repository. You can read about that at getting started with the OpenHatch code.

Figure out what kind of bug tracker you're importing

To find the bug tracker import code, do:

   $ cd mysite/customs/bugtrackers/

All our code lives inside "mysite". "customs" contains code that handles the importing of data from other places on the Internet. (Get it? It's a pun.) "bugtrackers" holds one file per type of bug tracker.

You'll find one file per type of bug tracker. For example, if you're adding code to cause us to import data from a bug tracker that runs the Roundup software, you'll need to be editing roundup.py.

Edit the right file

Each file has two parts...

  • One simple bit of code per project bug tracker we download data from: This is what you want. It's usually toward the end of the file. This is usually a five-line Python class.
  • The raw code that goes out to the network and fetches data: This is probably not what you want.

To add a new bug tracker, take an existing bug tracker's short code snippet and copy-paste it, adjusting what you need to adjust. You'll definitely need to change the project name, and you'll probably need to provide URLs for fetching a list of bugs to import.

Submit a patch