I've gone through the online documents and believe I followed
everything correctly. When I set up my perforce repository in the
admin section of ReviewBoard I set the "path" to the output of "server
address" from doing a p4 info. In my case this looks something like
"perforce.mydomain.com:1666".
Server Error
On Feb 4, 1:18 pm, Isaac Wagner wrote:
> I've gone through the online documents and believe I followed
> everything correctly. When I set up my perforce repository in the
> admin section of ReviewBoard I set the "path" to the output of "server
> addre
un "post-review -d > output.html", you will get a nice HTML
> doc that will have a stack trace in it. I normally get the error 500 page
> when i need to update my perforce ticket number. I don't use my password i
> use the actual ticket in the repository admin page. You
I followed all the direction for setting up PyLucene with JCC and then
went to enable search in the admin panel, but it won't let me. It
says "PyLucene (with JCC) is required to enable search." But, I
already did that? Am I missing something?
--~--~-~--~~~---~--~---
> --
> Christian Hammond - chip...@chipx86.com
> VMware, Inc.
>
>
> On Wed, Feb 4, 2009 at 11:51 AM, Isaac Wagner wrote:
>>
>> Thanks. My perforce authentication was incorrect. Now my next
>> problem:
>>
>> The post-review submission happens OK with no
I had to restart apache for this setting to be available. Strange.
On Feb 4, 2:54 pm, Isaac Wagner wrote:
> I followed all the direction for setting up PyLucene with JCC and then
> went to enable search in the admin panel, but it won't let me. It
> says "PyLucene (with
My users have a real hard time going back to close a review once they have
submitted the code. Instead of my periodically auditing the open reviews it
would be nice to have reminder emails sent out at a configurable period.
Or, even just a button that I could click on to send reminder emails to
an
I used easy_install to install post-review. I see in the docs that each
user can use a .reviewboardrc file in their home directory to customize
settings, like REVIEWBOARD_URL. I've only got one Review Board server and
want to globally set the REVIEWBOARD_URL for all users, but don't want to
have
d submit a patch for this.
On Tue, Apr 28, 2009 at 10:51 AM, lepton wrote:
>
> Read the code, you will find you can put .reviewboardrc in /home
> then everyone can use it.(If all user's home dir is under /home
> directory)
>
> On Tue, Apr 28, 2009 at 09:52:32AM -040
ite a patch. ;)
>
> Paul Scott
> VMware SCM Team
>
> From: reviewboard@googlegroups.com [reviewbo...@googlegroups.com] On
> Behalf Of Isaac Wagner [geekyis...@gmail.com]
> Sent: Tuesday, April 28, 2009 6:52 AM
> To: reviewboar
I might have missed it, but I can't seem to find a roadmap on your web
site. Is there a planned timeline for the various releases? I am anxiously
waiting for some of the features coming in 2.0. Specifically, issue 421 on
the bug tracking list. My users never close their review requests without
I am in the midst of setting up a review board instance, but hit this
snag. When I try to install the python p4 bindings I get an error:
# easy_install P4PythonInstaller
Searching for P4PythonInstaller
Reading http://pypi.python.org/simple/P4PythonInstaller/
Reading http://www.review-board.org/
12 matches
Mail list logo
