Hi All,
I have installed and configured ReviewBoard.
The problem i'm facing is with Virtual hosting. I'm using
the apache-mod_python conf file. I have installed and configured
Bugzilla,Mediawiki and SVN on the same server.
When i restarted https server
Hi,
Is it possible to use both LDAP and standard authentications?
This is the description of my problem:
1. in the institute we have LDAP server
2. the institute does some work with the external peple
Is it possible for internal to use existing LDAP and to provision the
rest in the standard
I'm investigating setting up reviewboard at my work to put a decent
code review process in place, and am looking to automate some steps.
In particular what I'd like to do is have pre-putback checks on the
repository server (currently subversion though I'm looking to convert
this to git) which
Hi,
I am considering integrating Review Board for my current project.
However, before doing so, I need to determine whether or not it will
place nicely with our current authentication process. All
authentication for every tool on our project revolves around the
authentication scheme for our XMPP
Hi,
We use SVN for source control. I have a bunch of newly written code in
new java files that are not yet committed in subversion. I want to
review the code in these files using ReviewBoard, but I'm wondering
how to create diff for these files since they do not have a prior
version (these are
ms wrote:
We use SVN for source control. I have a bunch of newly written code in
new java files that are not yet committed in subversion. I want to
review the code in these files using ReviewBoard, but I'm wondering
how to create diff for these files since they do not have a prior
version
abrightwell wrote:
I am considering integrating Review Board for my current project.
However, before doing so, I need to determine whether or not it will
place nicely with our current authentication process. All
authentication for every tool on our project revolves around the
authentication
Adam wrote:
However what I'm not seeing is any scriptable way of checking the
status of a review. Does something like this exist and I'm just not
finding it?
http://www.reviewboard.org/docs/manual/dev/webapi/ or you could hit the
database directly (using raw SQL or the Django ORM).
post-review has the --revision-range argument, but this does not work
(as far as I remember - or rather, last time I checked this some while
ago), if you specify lower revision numbers than the initial. If you
want do put whole files up for review, you'd normally want something
ala:
svn diff -r
FWIW, this is the post-receive hook I hacked up - maybe this will be
useful to someone else out there. On a `git push`, it will create
review requests for each (non-merge) commit. Some notes:
- It works with an unmodified postreview.py.
- It runs on bare git repositories.
- It sets the summary
Hi Aleksandar,
Our auth always falls back to standard auth for any users that aren't
in LDAP. However, we hide the registration page when using LDAP. It's
possible to add the user manually in the admin UI though. Would this
be sufficient, or is the registration form required in your setup?
Comment #1 on issue 1673 by l.holst: post-review revision-range doesn't
handle single revision as advertised
http://code.google.com/p/reviewboard/issues/detail?id=1673
I can confirm this issue.
I’m using post-review on a Mercurial repository. I wonder if there’s a
workaround.
--
You
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 1762 by tedmjohnson: Publish/Discard buttons don't load with
Safari 5.0.1
http://code.google.com/p/reviewboard/issues/detail?id=1762
*NOTE: Do not post confidential information in this bug report.*
What version are you
13 matches
Mail list logo