Bug tracker import code (moved): Difference between revisions
Content added Content deleted
No edit summary |
No edit summary |
||
Line 1: | Line 1: | ||
Here's what you need to know |
Here's what you need to know |
||
== One file per style of bug tracker == |
|||
⚫ | |||
* We write tests in mysite/customs/tests.py for each bug tracker type. |
|||
⚫ | |||
The Roundup code is instructive. Look at that in your favorite editor. You'll see: |
|||
⚫ | |||
* class RoundupTracker |
|||
⚫ | |||
The rest of that file is trivial subclasses that pre-fill the data to __init__(). |
The rest of that file is trivial subclasses that pre-fill the data to __init__(). We have one subclass per bug tracker we pull data from. |
||
== Then, once a day == |
|||
So if you want to add a new Roundup-based bug tracker, add a new subclass to that file, and submit a patch. |
|||
We have a cron job on the server that calls the code in <code>mysite/customs/management/commands/customs_daily_tasks.py</code> every night. |
|||
⚫ | |||
== How to add a new bug tracker == |
|||
That means that if you want to add code pull data from a bug tracker we already support, you just have to write a very simple subclass. For Roundup, for example, add a few lines to the end of mysite/customs/bugtrackers/roundup.py. Then submit a patch. |
|||
If you want to write support for an entirely new type of bug tracker, you'll have to write a new class. Before we merge it, we'll need some tests, but we can help you write the tests. Submit your patches as you go, and we can review/merge quickly! |
|||
⚫ | |||
[[Category:Hacking OpenHatch]] |
[[Category:Hacking OpenHatch]] |