I modified the base code for reviewboard. Its one small change in the webapi
code to trigger a generate_summary call when the close->submitted action is
Then a new file which contains the generate_summary code and its appropriate
template. The email code was used as the inspiration, and subtle
modifications were made to suit the layout I thought best for the summary.
This file is then written to the local disk and I have separate automation
which pushes it into our bugtracking system.
On Fri, Aug 20, 2010 at 12:48 AM, J Arrizza <cppge...@gmail.com> wrote:
> Sorry for taking so long to back to you, got tied up on other stuff.
> Very nice. You modified the base code in some spot or is the review summary
> generation already a part of RB 1.07?
> On Wed, Aug 18, 2010 at 2:22 PM, Scott Quesnelle <
> scott.quesne...@gmail.com> wrote:
>> I have an implementation in my deployment which generates a review summary
>> when the review is closed, and it writes the summary to a file that is named
>> based on the bugid(s) provided. A separate script runs and talks to the bug
>> tracking system and updates the appropriate bug(s) with the review summary
>> in a standardized enclosure.
>> This is currently running on RB 1.0.
> blog: http://arrizza.blogspot.com/
> web: http://www.arrizza.com/
> Want to help the Review Board project? Donate today at
> Happy user? Let us know at http://www.reviewboard.org/users/
> To unsubscribe from this group, send email to
> For more options, visit this group at
Want to help the Review Board project? Donate today at
Happy user? Let us know at http://www.reviewboard.org/users/
To unsubscribe from this group, send email to
For more options, visit this group at