The problem with reviewboard is it's a large django app, and i think it would be bad idea to attach it to rhodecode, hg-review on the other hand provides a nice api which would easily integrate with rhodecode, but only for mercurial.
We are using ReviewBoard. It can easily use Rhodecode as the source repository.
Give it a try!
@striker69: We are using ReviewBoard with SVN successfully and I've added many of our repos from RhodeCode into it. We are running into issues where the majority of the uploaded patch files make ReviewBoard blow up. Have you run into this or was there anything special you had to do to get ReviewBoard and RhodeCode to play nicely together?
Implemented in beta, notification system will be a separate task
@dstockto We have never had any issues with Rhodecode & Reviewboard. We use it with the TortoiseHG integration. The only thing, is that you must push the modifications to the server prior to creating the review. But that works well.
Former userAccount Deleted
@striker69 - We are using a "golden" central repo which doesn't receive the changesets until they've passed through QA successfully. We've got review board set up against the golden repo. The developers work based on a "stable" bookmark that exists in golden and moves along as the changes get through QA. Without exception, diffs or "hg postreview" when Review Board is configured to use the Rhodecode URL fail with a stack trace about being unable to apply the diff.
We did find a way around it though. We also set up hgwebdir.cgi (the one that comes with mercurial) to serve up all the same repos Rhodecode does (read-only though). When we point review board to the hgwebdir URLs the diffs work whether it's postreview or a diff. That would lead me to believe that the way Review Board interacts with the repos it gets a slightly different response or something that Review Board cannot deal with from Rhodecode that it doesn't get from hgwebdir.
@striker69 - The comment above is from me. I was apparently not logged in.
@dstockto that sound like a bug for me, the raw-diff pages suppose to be 1:1 with hgweb format, maybe we're missing something here ?
@dstockto Do you have more information on the error - stack trace, logs, others? May be this could help to pinpoint the problem.
@striker69 - I will set up a review board pointing to rhode code on Monday and post the stack trace here then.
@striker69 @dstockto you should also test drive code review in 1.3 beta :), i need some feedback.
Here's the stack trace I see when I try to do a view diff when I've submitted a patch/diff for a Review Board that is configured to point to Rhodecode:
The patch to 'feature20.txt' didn't apply cleanly. The temporary files have been left in '/tmp/reviewboard.bV0KsF' for debugging purposes. `patch` returned: patching file /tmp/reviewboard.bV0KsF/tmpVtBTej Hunk #1 FAILED at 2. 1 out of 1 hunk FAILED -- saving rejects to file /tmp/reviewboard.bV0KsF/tmpVtBTej-new.rej
My review is being submitted using the Diff files using both TortoiseHG and hg postreview.
But when I click on View Diff, I'm getting the 'patch not applied cleanly' error and I'm not sure on what has to be done.
Another information is that, I've not pushed my changes to the server yet. I dint push it because, earlier to RhodeCode, I was just using the hgweb.cgi and ReviewBoard was working fine with it. But after moving to Rhodecode, I got all the security that I had always wanted but, ReviewBoard's View Diff alone is not working.
Also, please do let me know if you need any further information, I will definitely put them up as I do not know what all information you would be needing.
Please post original diff generated (that used to work fine) and the same diff from rhodecode, please post them as original filenames, i'll compare and see what can be the cause.