I have a ReviewBoard installation configured at https://example.com/rb.
However, whenever I try to publish drafts or review requests, a
request is made to http://example.com/rb/api/(whatever) instead. My
browsers (as expected) barf on this. When I disable SSL, obviously
things work fine. How do I c
That would be fantastic. We use HP Quality Center (jury is still out on the
quality post of the name) and I'm takes with automating that as well.
On Nov 4, 2011 7:45 PM, "Tucker" wrote:
> Any chance you could share your diff for updating your tracker? We're
> using JIRA and I've had to become pl
Hello again --
We just tried using the NFS method suggested by Maciek. While
ReviewBoard is happy with this configuration, it breaks "post-
review". The post-review tool uses origin.url and ReviewBoard
complains that this repository does not exist. Because of this, it's
not really a workable so
Any chance you could share your diff for updating your tracker? We're
using JIRA and I've had to become plenty familiar with the SOAP API.
As I'm lazy and you've already done a bit of the work, I was hoping I
could piggy back of your efforts. I've not had the time to dive in
and find out how to e
I personally do two things. One carrot, one stick.
Stick first. I just sort reviews based on last updated time and look for
anyone that has more then 2 or 3 reviews of more then a certain age. I then
have a somewhat standard form letter that I mail them. It reminds them of
the process needs of thi
On Nov 4, 11:16 am, Christian Hammond wrote:
> SSH is supposed to work. We use it (for repo verification, though you still
> need the cgit, etc. method for getting files).
>
> You'd need to go into RB and generate a new SSH key and then configure it
> for access on the git server. Should in theory
Reinstalling with easy_install did not fix it.
One person from #django room recommened to use pip to get things done
correctly. I'm sure easy_install misses some of the entries that pip does.
Did, easy_install pip
and did all the reinstall with pip.
I did rebooted the machine now and checked it
Hi Martin,
There's no feature, current or planned, for this. You'd need to patch your
copy for this. In the next release, this would be able to be an extension,
but that'll be a while still.
Christian
On Friday, November 4, 2011, Martin wrote:
> Hi group, I want to check if summary of each new
SSH is supposed to work. We use it (for repo verification, though you still
need the cgit, etc. method for getting files).
You'd need to go into RB and generate a new SSH key and then configure it
for access on the git server. Should in theory work then.
Christian
On Friday, November 4, 2011, M
Hmm, trying to figure out how that's different from what was recommended
before and why it only worked now.
If this is breaking on every restart, there's something very wrong with
your server. That should never happen. Consider it a red flag and do some
investigating.
Christian
On Friday, Novem
I'm not sure if SSH access is even supposed to work. From technical
standpoint it might not be welcome after all, given that misconfiguration
might expose ssh keys. The access methods that always worked flawlessly for
me are exporting repositories over http and direct file access. I wouldn't
bother
Help from #django irc channel helped to fix it.
Did the following, everything is backup.
After every restart if you go and see you will see the missing module.
Delete it and reinstall it. It will get it resolved.
rm -rf /usr/lib/python2.4/site-packages/recaptcha_client-1.0.6-py2.4.egg
pip install
Hi group, I want to check if summary of each new review request is
compliant with a defined structure.
It could be performed using regular expressions, for instance.
Does someone know if there is this feature or if there is a workaround to
do this?
Thanks in advance.
Regards.
MArtin.
--
Wan
Hi,
As far as I know, Gitolite requires SSH keys and ReviewBoard doesn't
support that type of connection to Git repositories. In my company, we
had to export Git repositories via NFS to the machine with ReviewBoard
hosting. And then, in ReviewBoard's configuration we had to specify a
path to the r
14 matches
Mail list logo
