[Buildbot-devel] perforce connection

[andrea crotti]

2012/8/22 John Hopkins <jhopkins at mozilla.com>:
> Hi, Andrea:
>
>
> On 12-08-21 6:32 PM, Andrea Crotti wrote:
>
> On 08/21/2012 09:37 PM, William Deegan wrote:
>
> Did you check the step log to see if the env variable shows up there?
> And/or what the command line is?
>
> -Bill
>
> What do you mean in the step log??
> I mean I am also passing the p4passwd, but to make sure I also did
>
> export P4PASSWD='mypass'
> buildbot restart
>
> and I even went with ssh on the manhole interface and yes, os.environ
> shows the variable set..
>
> Even more, I used the perforce official bindings and with the same
> dictionary/variables I can connect
> and login correctly.. So I have to check maybe what's the actual command
> that is sent, but how do I
> debug this?
> I tried to set a pdb.set_trace() but of course it doesn't work since
> it's run through twisted..
>
>
> It could be that your Perforce server's security level is set high enough
> (level 3) that the client now ignores the P4PASSWD environment variable.
> More details here:
>
>  http://www.perforce.com/perforce/r10.2/manuals/p4sag/03_superuser.html
>
> Security Level 3 says: "All password-based authentication is rejected.
> Users must use ticket-based authentication (p4 login).
> If you have scripts that rely on passwords, use p4 login to create a ticket
> valid for the user running the script, or use p4 login -p to display the
> value of a ticket that can be passed to Perforce commands as though it were
> a password (that is, either from the command line, or by setting P4PASSWD to
> the value of the valid ticket)."
>
> Hope that helps,
> John
>
>


Tried that too (setting the P4PASSWD to the ticket), but nothing..
I'll ask the perforce guys here if they have any idea, maybe it's
faster, but I don't think the security is set to that level.

And in general my machine is logged in with the same user and
workspace already, so it should just work out of the box, I don't
quite understand..