"Unable to find a Review Board server for this source code tree" after updating SVN from 1.6 to 1.8

5,666 views
Skip to first unread message

Dandy Calaoagan

unread,
Jul 10, 2014, 1:57:26 AM7/10/14
to revie...@googlegroups.com
Hi,


I have a setup of review board working before (Python 2.7, Slik Subversion 1.6.17, Tortoise 1.6.17, RBTools 0.4.2) in my computer. I recently tried setting up a new one with the following versions - Python 2.7, Slik Subversion 1.8.x, Tortoise 1.8.x, and RBTools 0.4.2.

When doing a "post-review" in the root directory of my code, everything works fine. The problem is that when doing it in the sub-folders, I get a "Unable to find a Review Board server for this source code tree" message. I think this is because when using SVN 1.8 version, a ".svn" folder is no longer created in each sub-folders. 

It works if I specify a server together with the "post-review" command, but it's kind of a hassle knowing that it works before by simply typing "post-review". I also saw a solution before indicating that a ".reviewboardrc" file should be created, but for the same reason with the first approach, I'm hesitant to do this. 

Is there a way with my current setup that I'll be able to create a review by going to the sub folders and only typing "post-review"?


Thanks!

David Trowbridge

unread,
Jul 10, 2014, 9:18:02 PM7/10/14
to reviewboard
Can you run with --debug and reply with the output?

I suspect it's finding the repository correctly, but just doesn't know about your server (in which case adding a .reviewboardrc file to the root of the checkout is the correct solution).

I also highly recommend upgrading to the latest rbtools release and switching from 'post-review' to 'rbt post'.

-David


--
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/d/optout.

Dandy Calaoagan

unread,
Jul 11, 2014, 1:03:13 AM7/11/14
to revie...@googlegroups.com
I upgraded the rb tools I'm using to 0.6. However, 'rbt post' doesn't work even when doing it in the root directory of the source code ("Error creating review request: The repository pat
h specified is not in the list of known repositories (HTTP 400, API Error 206)").

Anyway, below is the output when doing 'rbt post' (or 'post-review') with the debug on.

c:\trunk\applications\source>rbt post --debug
>>> RBTools 0.6
>>> Python 2.7.2 (default, Jun 12 2011, 15:08:59) [MSC v.1500 32 bit (Intel)]
>>> Running on Windows-7-6.1.7601-SP1
>>> Home = C:\Users\Dandy.Calaoagan\AppData\Roaming
>>> Current directory = c:\trunk\applications\source
>>> Checking for a Subversion repository...
>>> Running: svn info --non-interactive
>>> Running: diff --version
>>> repository info: Path: https://svne1.access.uvn.com/isource/svnroot/EMU_SC_PLANE_DBase path: /trunk/applications/source, Supports changesets: False
>>> Running: svn propget reviewboard:url https://svne1.access.uvn.com/isource/svnroot/EMU_SC_PLANE_D
Unable to find a Review Board server for this source code tree.

I compared this with the 'post-review' done on the root directory, and saw there was a difference in the 'reviewboard:url' value. In the correct one, the value of the said parameter was the root directory (c:\trunk)

David Trowbridge

unread,
Jul 11, 2014, 2:20:13 AM7/11/14
to reviewboard
OK, it's successfully finding the SVN repository, so the .svn directory .

I'd recommend adding a .reviewboardrc file to c:\trunk which has a SERVER="..." line listing your review board server URL.

-David

Dandy Calaoagan

unread,
Jul 11, 2014, 3:31:16 AM7/11/14
to revie...@googlegroups.com
It's working now. Thanks. 

Just curious though, what's the reason for needing the .reviewboardrc now in the later versions? My original/older setup didn't need one, and I didn't encounter any problem at all.

David Trowbridge

unread,
Jul 13, 2014, 3:33:59 PM7/13/14
to reviewboard
You said there was a difference in the reviewboard:url property between the two setups? That's probably what's responsible. That said, we highly recommend using .reviewboardrc over the older svn properties.

-David
Reply all
Reply to author
Forward
0 new messages