Re: post-review is it mandatory to pass "ssl" prefix in --p4-port option.

[chuck j]

Thanks David and I really appreciate your responses. I did searched review 
board forum to get the response for such basic questions when there are 
complex system are in place. Failing to get the answer we have emailed you 
for the answer. Unless we start using the tool within the organization and 
demonstrate to actual end user, how i can propose for the support contract 
to my company. I am doing POC and making it strong case within an 
organization to use such feature provided by this fabulous tool.

But its unfair to say that we are wasting your time.

Thanks again apologies for wasting your precious time.



On Saturday, April 20, 2013 1:31:51 PM UTC+5:30, David Trowbridge wrote:
>
> The contents within the quotes on that line should be the name that you 
> assigned to your repository entry in the reviewboard admin. If you named 
> the repository http://ssl:pf-sa-perforce:19773/ then that would be correct, 
> but that's kind of a funny name. I really can't say whether or not it's 
> correct, because it depends on what you put into the admin form.
>
>
> Please, please try things out and read the documentation before asking 
> your questions here. It would only take 30 seconds for you to have tested 
> if it's correct. You're really starting to waste our time, and unless you'd 
> like to enter into a support contract and pay us for our time, we can't 
> keep answering these sorts of basic questions.
>
> -David
>
>
> On Sat, Apr 20, 2013 at 12:56 AM, chuck j 
> > wrote:
>
>> Thanks i will try that option too.
>>
>> Please correct me if the .reviewboardrc content are correct.
>>
>> REPOSITORY = 'http://ssl:pf-sa-perforce:19773/'
>>
>>
>>
>> On Saturday, April 20, 2013 12:59:52 PM UTC+5:30, David Trowbridge wrote:
>>
>>> This is where you'd use a .reviewboardrc file with the REPOSITORY 
>>> setting or the --repository-url parameter. Please read the post-review 
>>> documentation for details.
>>>
>>> -David
>>>
>>>
>>> On Sat, Apr 20, 2013 at 12:26 AM, chuck j  wrote:
>>>
 But adding ssl gives me 

 >>> HTTP POSTing to http://svrb1.company.com/svrb/**
 api/review-requests/: 
 {'changenum': '191316', 'submit_as': 'chuck', 'repository': 
 'pf-sa-perforce:19773'}

 >>> Got API Error 206 (HTTP code 400): The repository path specified is 
 not in the list of known repositories

 >>> Error data: {u'stat': u'fail', u'repository': 
 u'pf-sa-perforce:19773', u'err': {u'msg': u'The repository path specified 
 is not in the list of known repositories', u'code': 206}}

 just let you know in reviewboard server repository is added with name *
 ssl:pf-sa-perforce:19773*

 Then its seems that somehow rbt is searching the repository with name 
 pf-sa-perforce:19773 which is incorrect. Any other solution you want me to 
 try.



 On Saturday, April 20, 2013 12:43:00 PM UTC+5:30, David Trowbridge 
 wrote:

> post-review will execute the 'p4' command using the port that you're 
> passing into --p4-port. If you have a valid P4PORT environment variable 
> that you'd prefer to use, don't pass --p4-port. Since it looks like the 
> server at pf-sa-perforce:19773 refuses non-SSL connections, then you 
> probably do need the ssl: prefix.
>
> -David
>
>
> On Sat, Apr 20, 2013 at 12:10 AM, chuck j  wrote:
>
>> Hi David,
>>
>> As you mentioned that adding prefix ssl to --p4-port is not required, 
>> i did that but i got message which ask me add ssl to P4PORT.
>>
>> DEBUG:root:Checking for a Perforce repository...
>> DEBUG:root:Running: p4 info
>>
>> DEBUG:root:Running: diff --version
>> DEBUG:root:repository info: Path: pf-sa-perforce:19773, Base path: 
>> None, Supports changesets: True
>>
>> INFO:root:Generating diff for changenum 191316
>> DEBUG:root:Running: p4 describe -s 191316
>>
>> post-review.exe  -o  --bugs-closed="TAI3039" --branch="MAIN" --server=
>> http://svrrb1.**company**.com/svr--submit-as=**chuck--description-file="c:\users\
>> **c**huck\appdata\local\temp\**tmpgqt**cfa" 191316 
>> --p4-port="pf-sa-perforce:**1977**3" 
>>
>> posting review request...
>> >>> RBTools 0.4.3
>>
>> >>> Python 2.5.4 (r254:67916, Dec 23 2008, 15:10:54) [MSC v.1310 32 
>> bit (Intel)]
>>
>> >>> Running on Windows-Vista-6.1.7601
>>
>> >>> Home = C:\Users\chuck\AppData\Roaming
>>
>> >>> Current Directory = d:\pf_ch_ws
>>
>> >>> Checking the repository type. Errors shown below are mostly 
>> harmless.
>>
>> >>> Finished checking the repository type.
>>
>> >>> HTTP GETting api/info/
>>
>> Failed to execute command: ['p4', 'describe', '-s', '191316']
>>
>> ['Failed client connect, server using SSL.\n', 'Client must add SSL 
>> protocol

Re: post-review is it mandatory to pass "ssl" prefix in --p4-port option.

[David Trowbridge]

The contents within the quotes on that line should be the name that you
assigned to your repository entry in the reviewboard admin. If you named
the repository http://ssl:pf-sa-perforce:19773/ then that would be correct,
but that's kind of a funny name. I really can't say whether or not it's
correct, because it depends on what you put into the admin form.


Please, please try things out and read the documentation before asking your
questions here. It would only take 30 seconds for you to have tested if
it's correct. You're really starting to waste our time, and unless you'd
like to enter into a support contract and pay us for our time, we can't
keep answering these sorts of basic questions.

-David


On Sat, Apr 20, 2013 at 12:56 AM, chuck j  wrote:

> Thanks i will try that option too.
>
> Please correct me if the .reviewboardrc content are correct.
>
> REPOSITORY = 'http://ssl:pf-sa-perforce:19773/'
>
>
>
> On Saturday, April 20, 2013 12:59:52 PM UTC+5:30, David Trowbridge wrote:
>
>> This is where you'd use a .reviewboardrc file with the REPOSITORY setting
>> or the --repository-url parameter. Please read the post-review
>> documentation for details.
>>
>> -David
>>
>>
>> On Sat, Apr 20, 2013 at 12:26 AM, chuck j  wrote:
>>
>>> But adding ssl gives me
>>>
>>> >>> HTTP POSTing to 
>>> >>> http://svrb1.company.com/svrb/**api/review-requests/:
>>> {'changenum': '191316', 'submit_as': 'chuck', 'repository':
>>> 'pf-sa-perforce:19773'}
>>>
>>> >>> Got API Error 206 (HTTP code 400): The repository path specified is
>>> not in the list of known repositories
>>>
>>> >>> Error data: {u'stat': u'fail', u'repository':
>>> u'pf-sa-perforce:19773', u'err': {u'msg': u'The repository path specified
>>> is not in the list of known repositories', u'code': 206}}
>>>
>>> just let you know in reviewboard server repository is added with name *
>>> ssl:pf-sa-perforce:19773*
>>>
>>> Then its seems that somehow rbt is searching the repository with name
>>> pf-sa-perforce:19773 which is incorrect. Any other solution you want me to
>>> try.
>>>
>>>
>>>
>>> On Saturday, April 20, 2013 12:43:00 PM UTC+5:30, David Trowbridge wrote:
>>>
 post-review will execute the 'p4' command using the port that you're
 passing into --p4-port. If you have a valid P4PORT environment variable
 that you'd prefer to use, don't pass --p4-port. Since it looks like the
 server at pf-sa-perforce:19773 refuses non-SSL connections, then you
 probably do need the ssl: prefix.

 -David


 On Sat, Apr 20, 2013 at 12:10 AM, chuck j  wrote:

> Hi David,
>
> As you mentioned that adding prefix ssl to --p4-port is not required,
> i did that but i got message which ask me add ssl to P4PORT.
>
> DEBUG:root:Checking for a Perforce repository...
> DEBUG:root:Running: p4 info
>
> DEBUG:root:Running: diff --version
> DEBUG:root:repository info: Path: pf-sa-perforce:19773, Base path:
> None, Supports changesets: True
>
> INFO:root:Generating diff for changenum 191316
> DEBUG:root:Running: p4 describe -s 191316
>
> post-review.exe  -o  --bugs-closed="TAI3039" --branch="MAIN" --server=
> http://svrrb1.**company**.com/svr--submit-as=**chuck--description-file="c:\users\
> **c**huck\appdata\local\temp\**tmpgqt**cfa" 191316
> --p4-port="pf-sa-perforce:**1977**3"
>
> posting review request...
> >>> RBTools 0.4.3
>
> >>> Python 2.5.4 (r254:67916, Dec 23 2008, 15:10:54) [MSC v.1310 32
> bit (Intel)]
>
> >>> Running on Windows-Vista-6.1.7601
>
> >>> Home = C:\Users\chuck\AppData\Roaming
>
> >>> Current Directory = d:\pf_ch_ws
>
> >>> Checking the repository type. Errors shown below are mostly
> harmless.
>
> >>> Finished checking the repository type.
>
> >>> HTTP GETting api/info/
>
> Failed to execute command: ['p4', 'describe', '-s', '191316']
>
> ['Failed client connect, server using SSL.\n', 'Client must add SSL
> protocol prefix to P4PORT.\n']
>
> Please help.
>
> -Chuck
>
>
> On Saturday, April 20, 2013 12:11:00 AM UTC+5:30, David Trowbridge
> wrote:
>
>> If the p4port on the client matches that on the server, it will use
>> that to figure out which repository to post against.  If it doesn't 
>> (which
>> is what you're describing), you need to specify it manually, either with
>> command-line arguments or a .reviewboardrc file.
>> -David
>>
>>
>> On Fri, Apr 19, 2013 at 11:38 AM, chuck j  wrote:
>>
>>> Hi David,
>>>
>>> But while posting to non ssl base reviewboard i didn't require
>>> .reviewbaordrc. why it's require for this? where this file should be
>>> present. What should be content of .reviewboardrc.
>>>
>>> -chuck.
>>>
>>>
>>>
>>> On Frid

Re: post-review is it mandatory to pass "ssl" prefix in --p4-port option.

[chuck j]

Thanks i will try that option too.

Please correct me if the .reviewboardrc content are correct.

REPOSITORY = 'http://ssl:pf-sa-perforce:19773/'


On Saturday, April 20, 2013 12:59:52 PM UTC+5:30, David Trowbridge wrote:
>
> This is where you'd use a .reviewboardrc file with the REPOSITORY setting 
> or the --repository-url parameter. Please read the post-review 
> documentation for details.
>
> -David
>
>
> On Sat, Apr 20, 2013 at 12:26 AM, chuck j 
> > wrote:
>
>> But adding ssl gives me 
>>
>> >>> HTTP POSTing to http://svrb1.company.com/svrb/api/review-requests/: 
>> {'changenum': '191316', 'submit_as': 'chuck', 'repository': 
>> 'pf-sa-perforce:19773'}
>>
>> >>> Got API Error 206 (HTTP code 400): The repository path specified is 
>> not in the list of known repositories
>>
>> >>> Error data: {u'stat': u'fail', u'repository': 
>> u'pf-sa-perforce:19773', u'err': {u'msg': u'The repository path specified 
>> is not in the list of known repositories', u'code': 206}}
>>
>> just let you know in reviewboard server repository is added with name *
>> ssl:pf-sa-perforce:19773*
>>
>> Then its seems that somehow rbt is searching the repository with name 
>> pf-sa-perforce:19773 which is incorrect. Any other solution you want me to 
>> try.
>>
>>
>>
>> On Saturday, April 20, 2013 12:43:00 PM UTC+5:30, David Trowbridge wrote:
>>
>>> post-review will execute the 'p4' command using the port that you're 
>>> passing into --p4-port. If you have a valid P4PORT environment variable 
>>> that you'd prefer to use, don't pass --p4-port. Since it looks like the 
>>> server at pf-sa-perforce:19773 refuses non-SSL connections, then you 
>>> probably do need the ssl: prefix.
>>>
>>> -David
>>>
>>>
>>> On Sat, Apr 20, 2013 at 12:10 AM, chuck j  wrote:
>>>
 Hi David,

 As you mentioned that adding prefix ssl to --p4-port is not required, i 
 did that but i got message which ask me add ssl to P4PORT.

 DEBUG:root:Checking for a Perforce repository...
 DEBUG:root:Running: p4 info

 DEBUG:root:Running: diff --version
 DEBUG:root:repository info: Path: pf-sa-perforce:19773, Base path: 
 None, Supports changesets: True

 INFO:root:Generating diff for changenum 191316
 DEBUG:root:Running: p4 describe -s 191316

 post-review.exe  -o  --bugs-closed="TAI3039" --branch="MAIN" --server=
 http://svrrb1.**company.com/svr--submit-as=**chuck--description-file="c:\users\
 **chuck\appdata\local\temp\**tmpgqtcfa" 191316 
 --p4-port="pf-sa-perforce:**19773" 

 posting review request...
 >>> RBTools 0.4.3

 >>> Python 2.5.4 (r254:67916, Dec 23 2008, 15:10:54) [MSC v.1310 32 bit 
 (Intel)]

 >>> Running on Windows-Vista-6.1.7601

 >>> Home = C:\Users\chuck\AppData\Roaming

 >>> Current Directory = d:\pf_ch_ws

 >>> Checking the repository type. Errors shown below are mostly 
 harmless.

 >>> Finished checking the repository type.

 >>> HTTP GETting api/info/

 Failed to execute command: ['p4', 'describe', '-s', '191316']

 ['Failed client connect, server using SSL.\n', 'Client must add SSL 
 protocol prefix to P4PORT.\n']

 Please help.

 -Chuck


 On Saturday, April 20, 2013 12:11:00 AM UTC+5:30, David Trowbridge 
 wrote:

> If the p4port on the client matches that on the server, it will use 
> that to figure out which repository to post against.  If it doesn't 
> (which 
> is what you're describing), you need to specify it manually, either with 
> command-line arguments or a .reviewboardrc file.
> -David
>
>
> On Fri, Apr 19, 2013 at 11:38 AM, chuck j  wrote:
>
>> Hi David,
>>
>> But while posting to non ssl base reviewboard i didn't require 
>> .reviewbaordrc. why it's require for this? where this file should be 
>> present. What should be content of .reviewboardrc.
>>
>> -chuck.
>>
>>
>>
>> On Friday, April 19, 2013 2:05:56 PM UTC+5:30, David Trowbridge wrote:
>>>
>>> post-review (and rbt post) shouldn't require the ssl: prefix, but 
>>> you probably will want to create a .reviewboardrc with the repository 
>>> name.
>>>
>>> -David
>>>
>>>
>>> On Fri, Apr 19, 2013 at 1:31 AM, chuck j  wrote:
>>>
 Hi All,

 For ssl enabled perforce, while posting a review request, is it 
 mandatory to pass --p4-port='ssl:pf-server:1234' or normal port i.e 
 --p4-port=pf-sserver:1234' will work?

 Regards,
 Chuck.

 -- 
 Want to help the Review Board project? Donate today at 
 http://www.reviewboard.org/**don**ate/
 Happy user? Let us know at 
 http://www.reviewboard.org/**use**rs/
 -~--~~---

Re: post-review is it mandatory to pass "ssl" prefix in --p4-port option.

[David Trowbridge]

This is where you'd use a .reviewboardrc file with the REPOSITORY setting
or the --repository-url parameter. Please read the post-review
documentation for details.

-David


On Sat, Apr 20, 2013 at 12:26 AM, chuck j  wrote:

> But adding ssl gives me
>
> >>> HTTP POSTing to http://svrb1.company.com/svrb/api/review-requests/:
> {'changenum': '191316', 'submit_as': 'chuck', 'repository':
> 'pf-sa-perforce:19773'}
>
> >>> Got API Error 206 (HTTP code 400): The repository path specified is
> not in the list of known repositories
>
> >>> Error data: {u'stat': u'fail', u'repository': u'pf-sa-perforce:19773',
> u'err': {u'msg': u'The repository path specified is not in the list of
> known repositories', u'code': 206}}
>
> just let you know in reviewboard server repository is added with name *
> ssl:pf-sa-perforce:19773*
>
> Then its seems that somehow rbt is searching the repository with name
> pf-sa-perforce:19773 which is incorrect. Any other solution you want me to
> try.
>
>
>
> On Saturday, April 20, 2013 12:43:00 PM UTC+5:30, David Trowbridge wrote:
>
>> post-review will execute the 'p4' command using the port that you're
>> passing into --p4-port. If you have a valid P4PORT environment variable
>> that you'd prefer to use, don't pass --p4-port. Since it looks like the
>> server at pf-sa-perforce:19773 refuses non-SSL connections, then you
>> probably do need the ssl: prefix.
>>
>> -David
>>
>>
>> On Sat, Apr 20, 2013 at 12:10 AM, chuck j  wrote:
>>
>>> Hi David,
>>>
>>> As you mentioned that adding prefix ssl to --p4-port is not required, i
>>> did that but i got message which ask me add ssl to P4PORT.
>>>
>>> DEBUG:root:Checking for a Perforce repository...
>>> DEBUG:root:Running: p4 info
>>>
>>> DEBUG:root:Running: diff --version
>>> DEBUG:root:repository info: Path: pf-sa-perforce:19773, Base path: None,
>>> Supports changesets: True
>>>
>>> INFO:root:Generating diff for changenum 191316
>>> DEBUG:root:Running: p4 describe -s 191316
>>>
>>> post-review.exe  -o  --bugs-closed="TAI3039" --branch="MAIN" --server=
>>> http://svrrb1.**company.com/svr--submit-as=**chuck--description-file="c:\users\
>>> **chuck\appdata\local\temp\**tmpgqtcfa" 191316
>>> --p4-port="pf-sa-perforce:**19773"
>>>
>>> posting review request...
>>> >>> RBTools 0.4.3
>>>
>>> >>> Python 2.5.4 (r254:67916, Dec 23 2008, 15:10:54) [MSC v.1310 32 bit
>>> (Intel)]
>>>
>>> >>> Running on Windows-Vista-6.1.7601
>>>
>>> >>> Home = C:\Users\chuck\AppData\Roaming
>>>
>>> >>> Current Directory = d:\pf_ch_ws
>>>
>>> >>> Checking the repository type. Errors shown below are mostly harmless.
>>>
>>> >>> Finished checking the repository type.
>>>
>>> >>> HTTP GETting api/info/
>>>
>>> Failed to execute command: ['p4', 'describe', '-s', '191316']
>>>
>>> ['Failed client connect, server using SSL.\n', 'Client must add SSL
>>> protocol prefix to P4PORT.\n']
>>>
>>> Please help.
>>>
>>> -Chuck
>>>
>>>
>>> On Saturday, April 20, 2013 12:11:00 AM UTC+5:30, David Trowbridge wrote:
>>>
 If the p4port on the client matches that on the server, it will use
 that to figure out which repository to post against.  If it doesn't (which
 is what you're describing), you need to specify it manually, either with
 command-line arguments or a .reviewboardrc file.
 -David


 On Fri, Apr 19, 2013 at 11:38 AM, chuck j  wrote:

> Hi David,
>
> But while posting to non ssl base reviewboard i didn't require
> .reviewbaordrc. why it's require for this? where this file should be
> present. What should be content of .reviewboardrc.
>
> -chuck.
>
>
>
> On Friday, April 19, 2013 2:05:56 PM UTC+5:30, David Trowbridge wrote:
>>
>> post-review (and rbt post) shouldn't require the ssl: prefix, but you
>> probably will want to create a .reviewboardrc with the repository name.
>>
>> -David
>>
>>
>> On Fri, Apr 19, 2013 at 1:31 AM, chuck j  wrote:
>>
>>> Hi All,
>>>
>>> For ssl enabled perforce, while posting a review request, is it
>>> mandatory to pass --p4-port='ssl:pf-server:1234' or normal port i.e
>>> --p4-port=pf-sserver:1234' will work?
>>>
>>> Regards,
>>> Chuck.
>>>
>>> --
>>> Want to help the Review Board project? Donate today at
>>> http://www.reviewboard.org/**don**ate/
>>> Happy user? Let us know at 
>>> http://www.reviewboard.org/**use**rs/
>>> -~--~~~~--~~--~--~---
>>> To unsubscribe from this group, send email to
>>> reviewboard...@googlegroups.**co**m
>>> For more options, visit this group at http://groups.google.com/**
>>> group**/reviewboard?hl=en
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "reviewboard" group.
>>> To un

Re: post-review is it mandatory to pass "ssl" prefix in --p4-port option.

[chuck j]

But adding ssl gives me 

>>> HTTP POSTing to http://svrb1.company.com/svrb/api/review-requests/: 
{'changenum': '191316', 'submit_as': 'chuck', 'repository': 
'pf-sa-perforce:19773'}

>>> Got API Error 206 (HTTP code 400): The repository path specified is not 
in the list of known repositories

>>> Error data: {u'stat': u'fail', u'repository': u'pf-sa-perforce:19773', 
u'err': {u'msg': u'The repository path specified is not in the list of 
known repositories', u'code': 206}}

just let you know in reviewboard server repository is added with name *
ssl:pf-sa-perforce:19773*

Then its seems that somehow rbt is searching the repository with name 
pf-sa-perforce:19773 which is incorrect. Any other solution you want me to 
try.


On Saturday, April 20, 2013 12:43:00 PM UTC+5:30, David Trowbridge wrote:
>
> post-review will execute the 'p4' command using the port that you're 
> passing into --p4-port. If you have a valid P4PORT environment variable 
> that you'd prefer to use, don't pass --p4-port. Since it looks like the 
> server at pf-sa-perforce:19773 refuses non-SSL connections, then you 
> probably do need the ssl: prefix.
>
> -David
>
>
> On Sat, Apr 20, 2013 at 12:10 AM, chuck j 
> > wrote:
>
>> Hi David,
>>
>> As you mentioned that adding prefix ssl to --p4-port is not required, i 
>> did that but i got message which ask me add ssl to P4PORT.
>>
>> DEBUG:root:Checking for a Perforce repository...
>> DEBUG:root:Running: p4 info
>>
>> DEBUG:root:Running: diff --version
>> DEBUG:root:repository info: Path: pf-sa-perforce:19773, Base path: None, 
>> Supports changesets: True
>>
>> INFO:root:Generating diff for changenum 191316
>> DEBUG:root:Running: p4 describe -s 191316
>>
>> post-review.exe  -o  --bugs-closed="TAI3039" --branch="MAIN" --server=
>> http://svrrb1.company.com/svr--submit-as=chuck--description-file="c:\users\chuck\appdata\local\temp\tmpgqtcfa";
>>  191316 
>> --p4-port="pf-sa-perforce:19773" 
>>
>> posting review request...
>> >>> RBTools 0.4.3
>>
>> >>> Python 2.5.4 (r254:67916, Dec 23 2008, 15:10:54) [MSC v.1310 32 bit 
>> (Intel)]
>>
>> >>> Running on Windows-Vista-6.1.7601
>>
>> >>> Home = C:\Users\chuck\AppData\Roaming
>>
>> >>> Current Directory = d:\pf_ch_ws
>>
>> >>> Checking the repository type. Errors shown below are mostly harmless.
>>
>> >>> Finished checking the repository type.
>>
>> >>> HTTP GETting api/info/
>>
>> Failed to execute command: ['p4', 'describe', '-s', '191316']
>>
>> ['Failed client connect, server using SSL.\n', 'Client must add SSL 
>> protocol prefix to P4PORT.\n']
>>
>> Please help.
>>
>> -Chuck
>>
>>
>> On Saturday, April 20, 2013 12:11:00 AM UTC+5:30, David Trowbridge wrote:
>>
>>> If the p4port on the client matches that on the server, it will use that 
>>> to figure out which repository to post against.  If it doesn't (which is 
>>> what you're describing), you need to specify it manually, either with 
>>> command-line arguments or a .reviewboardrc file.
>>> -David
>>>
>>>
>>> On Fri, Apr 19, 2013 at 11:38 AM, chuck j  wrote:
>>>
 Hi David,

 But while posting to non ssl base reviewboard i didn't require 
 .reviewbaordrc. why it's require for this? where this file should be 
 present. What should be content of .reviewboardrc.

 -chuck.



 On Friday, April 19, 2013 2:05:56 PM UTC+5:30, David Trowbridge wrote:
>
> post-review (and rbt post) shouldn't require the ssl: prefix, but you 
> probably will want to create a .reviewboardrc with the repository name.
>
> -David
>
>
> On Fri, Apr 19, 2013 at 1:31 AM, chuck j  wrote:
>
>> Hi All,
>>
>> For ssl enabled perforce, while posting a review request, is it 
>> mandatory to pass --p4-port='ssl:pf-server:1234' or normal port i.e 
>> --p4-port=pf-sserver:1234' will work?
>>
>> Regards,
>> Chuck.
>>
>> -- 
>> Want to help the Review Board project? Donate today at 
>> http://www.reviewboard.org/**donate/
>> Happy user? Let us know at 
>> http://www.reviewboard.org/**users/
>> -~--~~~~--**~~--~--~---
>> To unsubscribe from this group, send email to 
>> reviewboard...@googlegroups.**com
>> For more options, visit this group at http://groups.google.com/**
>> group/reviewboard?hl=en
>> --- 
>> 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/**groups/opt_out
>> .
>>  
>>  
>>
>
>  -- 
 Want to help the Review Board project? Donate today at 
 http://www.reviewboard.org/**donate/

Review Board 1.7.7 released

[Christian Hammond]

Hi everyone,

We just released RB 1.7.7. It has some new features for admins, bug fixes,
an some good performance improvements.

Full info and a link to the release notes is on the news post at
http://www.reviewboard.org/news/2013/04/19/review-board-1-7-7-released/

Christian

-- 
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
Beanbag, Inc. - http://www.beanbaginc.com

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en
--- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: post-review is it mandatory to pass "ssl" prefix in --p4-port option.

[David Trowbridge]

post-review will execute the 'p4' command using the port that you're
passing into --p4-port. If you have a valid P4PORT environment variable
that you'd prefer to use, don't pass --p4-port. Since it looks like the
server at pf-sa-perforce:19773 refuses non-SSL connections, then you
probably do need the ssl: prefix.

-David


On Sat, Apr 20, 2013 at 12:10 AM, chuck j  wrote:

> Hi David,
>
> As you mentioned that adding prefix ssl to --p4-port is not required, i
> did that but i got message which ask me add ssl to P4PORT.
>
> DEBUG:root:Checking for a Perforce repository...
> DEBUG:root:Running: p4 info
>
> DEBUG:root:Running: diff --version
> DEBUG:root:repository info: Path: pf-sa-perforce:19773, Base path: None,
> Supports changesets: True
>
> INFO:root:Generating diff for changenum 191316
> DEBUG:root:Running: p4 describe -s 191316
>
> post-review.exe  -o  --bugs-closed="TAI3039" --branch="MAIN" --server=
> http://svrrb1.company.com/svr--submit-as=chuck--description-file="c:\users\chuck\appdata\local\temp\tmpgqtcfa";
>  191316
> --p4-port="pf-sa-perforce:19773"
>
> posting review request...
> >>> RBTools 0.4.3
>
> >>> Python 2.5.4 (r254:67916, Dec 23 2008, 15:10:54) [MSC v.1310 32 bit
> (Intel)]
>
> >>> Running on Windows-Vista-6.1.7601
>
> >>> Home = C:\Users\chuck\AppData\Roaming
>
> >>> Current Directory = d:\pf_ch_ws
>
> >>> Checking the repository type. Errors shown below are mostly harmless.
>
> >>> Finished checking the repository type.
>
> >>> HTTP GETting api/info/
>
> Failed to execute command: ['p4', 'describe', '-s', '191316']
>
> ['Failed client connect, server using SSL.\n', 'Client must add SSL
> protocol prefix to P4PORT.\n']
>
> Please help.
>
> -Chuck
>
>
> On Saturday, April 20, 2013 12:11:00 AM UTC+5:30, David Trowbridge wrote:
>
>> If the p4port on the client matches that on the server, it will use that
>> to figure out which repository to post against.  If it doesn't (which is
>> what you're describing), you need to specify it manually, either with
>> command-line arguments or a .reviewboardrc file.
>> -David
>>
>>
>> On Fri, Apr 19, 2013 at 11:38 AM, chuck j  wrote:
>>
>>> Hi David,
>>>
>>> But while posting to non ssl base reviewboard i didn't require
>>> .reviewbaordrc. why it's require for this? where this file should be
>>> present. What should be content of .reviewboardrc.
>>>
>>> -chuck.
>>>
>>>
>>>
>>> On Friday, April 19, 2013 2:05:56 PM UTC+5:30, David Trowbridge wrote:

 post-review (and rbt post) shouldn't require the ssl: prefix, but you
 probably will want to create a .reviewboardrc with the repository name.

 -David


 On Fri, Apr 19, 2013 at 1:31 AM, chuck j  wrote:

> Hi All,
>
> For ssl enabled perforce, while posting a review request, is it
> mandatory to pass --p4-port='ssl:pf-server:1234' or normal port i.e
> --p4-port=pf-sserver:1234' will work?
>
> Regards,
> Chuck.
>
> --
> Want to help the Review Board project? Donate today at
> http://www.reviewboard.org/**donate/
> Happy user? Let us know at 
> http://www.reviewboard.org/**users/
> -~--~~~~--**~~--~--~---
> To unsubscribe from this group, send email to
> reviewboard...@googlegroups.**com
> For more options, visit this group at http://groups.google.com/**
> group/reviewboard?hl=en
> ---
> 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/**groups/opt_out
> .
>
>
>

  --
>>> Want to help the Review Board project? Donate today at
>>> http://www.reviewboard.org/**donate/
>>> Happy user? Let us know at 
>>> http://www.reviewboard.org/**users/
>>> -~--~~~~--**~~--~--~---
>>> To unsubscribe from this group, send email to reviewboard...@**
>>> googlegroups.com
>>> For more options, visit this group at http://groups.google.com/**
>>> group/reviewboard?hl=en
>>> ---
>>> 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/**groups/opt_out
>>> .
>>>
>>>
>>>
>>
>>  --
> Want to help the Review Board project? Donate today at
> http://www.reviewboard.org/donate/
> Happy user? Let us know at http://www.reviewboard.org/users/
> -~--

Re: post-review is it mandatory to pass "ssl" prefix in --p4-port option.

[chuck j]

Hi David,

As you mentioned that adding prefix ssl to --p4-port is not required, i did 
that but i got message which ask me add ssl to P4PORT.

DEBUG:root:Checking for a Perforce repository...
DEBUG:root:Running: p4 info

DEBUG:root:Running: diff --version
DEBUG:root:repository info: Path: pf-sa-perforce:19773, Base path: None, 
Supports changesets: True

INFO:root:Generating diff for changenum 191316
DEBUG:root:Running: p4 describe -s 191316

post-review.exe  -o  --bugs-closed="TAI3039" --branch="MAIN" 
--server=http://svrrb1.company.com/svr--submit-as=chuck 
--description-file="c:\users\chuck\appdata\local\temp\tmpgqtcfa" 191316 
--p4-port="pf-sa-perforce:19773" 

posting review request...
>>> RBTools 0.4.3

>>> Python 2.5.4 (r254:67916, Dec 23 2008, 15:10:54) [MSC v.1310 32 bit 
(Intel)]

>>> Running on Windows-Vista-6.1.7601

>>> Home = C:\Users\chuck\AppData\Roaming

>>> Current Directory = d:\pf_ch_ws

>>> Checking the repository type. Errors shown below are mostly harmless.

>>> Finished checking the repository type.

>>> HTTP GETting api/info/

Failed to execute command: ['p4', 'describe', '-s', '191316']

['Failed client connect, server using SSL.\n', 'Client must add SSL 
protocol prefix to P4PORT.\n']

Please help.

-Chuck

On Saturday, April 20, 2013 12:11:00 AM UTC+5:30, David Trowbridge wrote:
>
> If the p4port on the client matches that on the server, it will use that 
> to figure out which repository to post against.  If it doesn't (which is 
> what you're describing), you need to specify it manually, either with 
> command-line arguments or a .reviewboardrc file.
> -David
>
>
> On Fri, Apr 19, 2013 at 11:38 AM, chuck j 
> > wrote:
>
>> Hi David,
>>
>> But while posting to non ssl base reviewboard i didn't require 
>> .reviewbaordrc. why it's require for this? where this file should be 
>> present. What should be content of .reviewboardrc.
>>
>> -chuck.
>>
>>
>>
>> On Friday, April 19, 2013 2:05:56 PM UTC+5:30, David Trowbridge wrote:
>>>
>>> post-review (and rbt post) shouldn't require the ssl: prefix, but you 
>>> probably will want to create a .reviewboardrc with the repository name.
>>>
>>> -David
>>>
>>>
>>> On Fri, Apr 19, 2013 at 1:31 AM, chuck j  wrote:
>>>
 Hi All,

 For ssl enabled perforce, while posting a review request, is it 
 mandatory to pass --p4-port='ssl:pf-server:1234' or normal port i.e 
 --p4-port=pf-sserver:1234' will work?

 Regards,
 Chuck.

 -- 
 Want to help the Review Board project? Donate today at 
 http://www.reviewboard.org/donate/
 Happy user? Let us know at http://www.reviewboard.org/users/
 -~--~~~~--~~--~--~---
 To unsubscribe from this group, send email to 
 reviewboard...@googlegroups.com
 For more options, visit this group at 
 http://groups.google.com/group/reviewboard?hl=en
 --- 
 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/groups/opt_out.
  
  

>>>
>>>  -- 
>> Want to help the Review Board project? Donate today at 
>> http://www.reviewboard.org/donate/
>> Happy user? Let us know at http://www.reviewboard.org/users/
>> -~--~~~~--~~--~--~---
>> To unsubscribe from this group, send email to 
>> reviewboard...@googlegroups.com 
>> For more options, visit this group at 
>> http://groups.google.com/group/reviewboard?hl=en
>> --- 
>> 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/groups/opt_out.
>>  
>>  
>>
>
>

-- 
Want to help the Review Board project? Donate today at 
http://www.reviewboard.org/donate/
Happy user? Let us know at http://www.reviewboard.org/users/
-~--~~~~--~~--~--~---
To unsubscribe from this group, send email to 
reviewboard+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/reviewboard?hl=en
--- 
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+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.