Hi,
We are using Review Board 1.7.1
I am getting "404 not found" error while giving the diff comment and before
publishing it.But the comment is getting saved.
Below is the API call it is making.
http://127.0.0.1:8000/api/review-requests/13/reviews/draft/?api_format=json
I guessed this is no
On Thu, 21 Mar 2013 00:12:30 +, "A.M."
wrote:
> Hello,
>
> Is it possible to use the rb API in 1.7.5 to get the changes to
reviewboard
> in the past X minutes (any review request changes)? I am creating a
review
> board poller which will then update a ticket system with links to
> reviewboard
On 2013-03-20 20:12, A.M. wrote:
Is it possible to use the rb API in 1.7.5 to get the changes to reviewboard
in the past X minutes (any review request changes)? I am creating a review
board poller which will then update a ticket system with links to
reviewboard.
I had previously made a reviewboa
Hello everyone,
In my project am trying to submit review request directly from
Perforce(version control system) to Review Board. So please can someone
suggest how to extract the fields from Perforce to Review Board.
Thanks
Shweta.
--
Want to help the Review Board project? Donate today
I'm not entirely sure what you're asking. What do you mean by "extract the
fields from Perforce to Review Board"?
-David
On Thu, Mar 21, 2013 at 10:38 AM, SHWETA AHER wrote:
> Hello everyone,
>
> In my project am trying to submit review request directly from
> Perforce(version control sys
Yes, that's currently expected. We don't intend to allow commenting on
diffs before the review request is public, but we have a long-standing bug
where it's allowed. Hopefully we'll fix that sometime soon, but for now,
you have to publish first.
-David
On Thu, Mar 21, 2013 at 6:49 AM, kvr wrot
We've got a somewhat odd perforce setup that has a single server that can
be addressed a number of ways:
server.eng.domain.net
server.domain.net
server.comany.com
I've patched the post-review tool so that it ignores the aliases, but
anytime I post a review to the server I get a server error ind
The best way to handle this is to set REPOSITORY in the .reviewboardrc in
order to force it to always find the right one.
-David
On Thu, Mar 21, 2013 at 4:35 PM, Lee Laborczfalvi wrote:
> We've got a somewhat odd perforce setup that has a single server that can
> be addressed a number of ways:
Yeah I have that - it's in my .reviewboardrc file...if I dump the server
log it ends with this:
2013-03-21 18:14:31,878 - ERROR - Error uploading new diff: A repository
was not found at the specified path.
Traceback (most recent call last):
File
"/usr/local/lib/python2.7/dist-packages/ReviewB
