Ideas needed regarding to RB bug tracker integration

Tomi Äijö

unread,

Feb 7, 2014, 9:07:54 PM2/7/14

to revie...@googlegroups.com

Hi,

My name is Tomi Äijö. I am attending the Facebook Open Academy this spring contributing to Review board. My student project has to do with Review board bug tracker integration (see issue https://code.google.com/p/reviewboard/issues/detail?id=193).

I would like to hear ideas and feature requests from the community regarding this project. I have been looking into the following bug trackers so far:

Google code: No public API any more (https://code.google.com/p/support/wiki/IssueTrackerAPI)

JIRA: Public API (https://bitbucket.org/bspeakmon/jira-python)

Trac: No officially supported API, there exists a plugin called XmlRpcPlugin that provides API but not actively maintained (http://trac-hacks.org/wiki/XmlRpcPlugin)

Bugzilla: Native XMLRPC interface (http://www.bugzilla.org/docs/3.6/en/html/api/Bugzilla/WebService/Server/XMLRPC.html)

Reading the issue 193 and its duplicates the following features seems to be the most desired:

- Posting a comment when a review request is linked to a bug

- Change the status of a bug according to the corresponding review request status

- Show information about the bug in Review board

Please share any ideas and comments regarding to this project!

Best regards,

Tomi Äijö

Javins, Walt

unread,

Feb 10, 2014, 4:26:32 PM2/10/14

to revie...@googlegroups.com

Hi Tomi,

We use the Review Board + Bugzilla power combo here at Isilon, and would definitely benefit from better integration between the two services. The bug links in RB are a great start, but as you’ve mentioned, there isn’t much discoverability from the standpoint of “I’m looking at a bug, what rrqs are associated with it?” Generally our developers will post a RB link in the bugs whiteboard when they have a fix under CR, but that solution is rather manual, tedious, and prone to being ignored.

I’d be glad to help out with design, implementation, or CR if you need assistance.

> I would like to hear ideas and feature requests from the community regarding this project. I have been looking into the following bug trackers so far:

The only other service at Isilon that falls in the same vein is RallyDev. I’m fine if Rally isn’t in the intitial batch though. As long as the RB integration framework is well designed, I can add a module for Rally later.

Walt

--
Get the Review Board Power Pack at http://www.reviewboard.org/powerpack/
---
Sign up for Review Board hosting at RBCommons: https://rbcommons.com/
---
Happy user? Let us know at http://www.reviewboard.org/users/
---
You received this message because you are subscribed to the Google Groups "reviewboard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reviewboard...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Gong Zhang

unread,

Feb 11, 2014, 3:15:49 PM2/11/14

to revie...@googlegroups.com

Hi Tomi,

Our team is using ReviewBoard + Jira + Jenkins right now, and although we can link the Jira ticket to a code review manually, it will be great if the review board can automatically create a Jira ticket for us when we submit a code review and automatically close that ticket once the code review is accepted. Does that make sence? Thanks!

markd...@gmail.com

unread,

Feb 11, 2014, 8:10:08 PM2/11/14

to revie...@googlegroups.com

I have integrated RB with our bug tracker, a heavily customized version of GNATS. I modified the RBBugTracker extension published by a student, I believe, a few years back.

That extension was built for google code, though the extension has a plug-in architecture so I added one for GNATS. It wasn't too much work to port to the latest RB version. Mostly the init() functions needed some tweaking - an extra argument as I recall.

The framework for trapping the relevant signals was already there, as well as a simple admin panel. I found it fairly simple to add a class for our bug tracker with a method to process the signals. Upon receipt of a signal I chose to simply exec existing scripts to modify the bug tracker. If you have a native Python API to your bug tracker you could go that way I suppose.

While this extension has been quite useful with RB 1.7.x, it will be even more useful with RB 2.0. The main reason is that you end up needing to communicate meta-data between the front-end (rbt post) and the back end (the bug tracker extension). Right now I do that with change descriptions but it's a little hacky.

I've not yet written a UI extension to display bug info in RB, though that would be desirable.

I've emailed at length with Christian, who's been a tremendous help, of course. If it helps I can help explain the modifications in more detail, and I'm hoping to publish the code diffs.

Regards
Mark Beyer
Juniper Networks