Yes, that's correct. Any user with read access will work.
-David
On Sun, Dec 29, 2013 at 10:50 PM, neel roy wrote:
> I know that's the usual procedure but that's not going to work because my
> organization do not want to create automation account which has read-only
> access. So I am taking an
I know that's the usual procedure but that's not going to work because my
organization do not want to create automation account which has read-only
access. So I am taking another route.. to use user's account who already
has read-only access... Now, since Christian said there is ticket based
au
You configure Review Board with one perforce user account (usually an
automation account of some sort). That account needs permission to read
changes and files, but doesn't write. Individual users don't enter their
own perforce credentials.
-David
On Sun, Dec 29, 2013 at 10:39 PM, neel roy wrot
Perfect. I have not decided which version to install but now it has to be
1.7.x :) BTW, before looking in the documentation I think the procedure
would be that user gives his\her own password in password field (which
reviewboard stores somewhere I guess), and enable ticket based auth and
that's
Hi Neel,
What version of Review Board are you running? Modern 1.7.x releases have a
checkbox for enabling ticket-based auth, and will auto-fetch a ticket as
needed.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbagi
Hi,
>From what I understand to use perforce with reviewboard, I have to login
with p4 -a -p, take the ticket that this command outputs to the screen, and
put it in the password field in reviewboard. Problem is tickets that are
generated in my organization expire in 24 hours (and we cannot have
