2118: Add p4ticket support in perforce backend

niles*****@gmai***** (Google Code) (Is this you? Claim this profile.)
Oct. 8, 2011
1623 
What version are you running?
1.5.5

What's the URL of the page containing the problem?


What steps will reproduce the problem?
1. While posting a reviewrequest using post-review tool getting below error

Error creating review request: HTTP 500

What is the expected output? What do you see instead?


What operating system are you using? What browser?

Linux RHEL el5

Please provide any additional information below.

Getting error as below 

    return lambda *args: self.run(cmd, *args)
  File "/usr/local/lib/python2.5/site-packages/P4.py", line 284, in run
    return P4API.P4Adapter.run(self, *self.__flatten(args))
P4Exception: [P4#run] Errors during command execution( "p4 describe -s 107805" )

        [Error]: Perforce password (P4PASSWD) invalid or unset.


Can someone advise what could be the issues here.

I also set the perforce repository properly (Home › Scmtools › Repositories ›), Does username and password required ?

here i am using perforce.

Also when i set the username and password the password field goes blank even after saving is it a default behavior
#1 gtu****@gmai***** (Google Code) (Is this you? Claim this profile.) 
Do you have a P4PASSWD environment variable set?  The previous company I worked for used perforce and it was stored in a dot file.  Since you're using Linux, try this:

$ export P4PASSWD='<your_password_here>'
(don't include the $, that denotes a prompt)

If that works, declare this in you $HOME/.bashrc by adding a line like this:

export P4PASSWD='<your_password_here>'
#2 niles*****@gmai***** (Google Code) (Is this you? Claim this profile.) 
Thank your for your prompt response.

We don't use P4PASSWD, for user it creates p4tickets. which contains the
user id and its ticket for respective user.

I got stuck now.

Also in the reviewboard administration section

Home <http://ccsdtool.na.mscsoftware.com/ccsdtool/admin/db/> ›
Scmtools<http://ccsdtool.na.mscsoftware.com/ccsdtool/admin/db/scmtools/>›
Repositories<http://ccsdtool.na.mscsoftware.com/ccsdtool/admin/db/scmtools/repository/>›
pf-sa-1666

Where the details of respository hosting is present does it requires any
configuration i have added.

 Hosting service: custom
  Repository type:Perforce
  Path: pf-sa.shsho.com:1666

Mirror Path:

Username: njaiswal

Password:
Does it requires anything else which i am missing.
#3 niles*****@gmai***** (Google Code) (Is this you? Claim this profile.) 
Thank your for your prompt response.

We don't use P4PASSWD, for user it creates p4tickets. which contains the user id and its ticket for respective user.

I got stuck now.

Also in the reviewboard administration section

Home › Scmtools › Repositories › pf-sa-1666

Where the details of respository hosting is present does it requires any configuration i have added.

Hosting service: custom
Repository type:Perforce
Path: pf-sa.shsho.com:1666

Mirror Path:

Username: njaiswal

Password:
Does it requires anything else which i am missing.
david
#4 david
  • -Type-Defect
    +Type-Enhancement
    +Component-SCMTools
  • +Add p4ticket support in perforce backend
#5 niles*****@gmai***** (Google Code) (Is this you? Claim this profile.) 
When can we expect the fix for this issue.
#6 niles*****@gmai***** (Google Code) (Is this you? Claim this profile.) 
Dear All,

With reference to issue reported 2118. I am still facing the issue with RB
1.6.1 where

Home <http://ccsdtool.na.mscsoftware.com/ccsdtool/admin/db/> ›
Scmtools<http://ccsdtool.na.mscsoftware.com/ccsdtool/admin/db/scmtools/>›
Repositories<http://ccsdtool.na.mscsoftware.com/ccsdtool/admin/db/scmtools/repository/>›
pf-sa-1666

Repository Hosting section password field appear to be empty, could some one
provide me workaround to make sure password enter should get visible (******
form) after save button is pressed.Regards,
Nilesh J
chipx86
#7 chipx86 
Hi Nilesh,

We don't yet support p4tickets. This would need to be written by someone with a p4ticket-enabled Perforce setup.
david
#8 david 
Actually, we have another issue open about this already.