Comment #7 on issue 88 by ted.dunning: integration with buildbot like  

Hudson (and presumably other continuous integration systems) makes it very  
easy to
have builds trigger pokes of other systems.  Thus there is an integration  
with JIRA
that puts a comment on all bugs in the change list of a build.

Hudson also handles patch builds well.  Apache projects use this  
extensively by
arranging for hudson to scan for issues that are in the "patch available"  
Hudson then downloads the patch, checks out the code, applies the patch and  
puts a
comment back on the original JIRA issue.

This structure could easily be adapted if there is a simple way for an  
outside system
to scan for new reviews and a simple API for posting comments.  The build  
could then sift through the reviews eliminating those it has already seen  
or which
refer to code not under a build watch.  Any new qualifying builds would  
then be built
and a summary posted.

You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:

You received this message because you are subscribed to the Google Groups 
"reviewboard-issues" group.
To post to this group, send email to
To unsubscribe from this group, send email to
For more options, visit this group at

Reply via email to