[p4perl] Problem using P4->FetchClient() (CALL#2151058)
Scott.Lavender at visiprise.com
Fri Sep 19 09:13:57 PDT 2008
Perforce - The Fast Software Configuration Management System.
Copyright 1995-2006 Perforce Software. All rights reserved.
Rev. P4/NTX86/2006.2/112639 (2006/12/14).
D:\P4Views\build_ProdTest\BuildSystem\production>p4.20062 login -s
Perforce password (P4PASSWD) invalid or unset.
User build logged in.
192.168.1.61:1666 (build) 704B4F108CECC0C498F30442404FFCB5
perforce.visiprise.com:1666 (build) 704B4F108CECC0C498F30442404FFCB5
Now I have two tickets, one with the IP address of the server and the
other with the DNS name.
I need to keep my existing build environment running, since all of our
product build run there. How can I set this up to run this version of P4
when I'm logged in as the new domain user, while still allowing the
other environment to run? Should I just place this p4.exe closer the
front of the new users PATH?
From: Tony Smith [mailto:tony at smee.org]
Sent: Friday, September 19, 2008 11:46 AM
To: p4perl at perforce.com; support at perforce.com
Cc: Scott Lavender
Subject: Re: [p4perl] Problem using P4->FetchClient() (CALL#2151058)
Thanks for all that.
On Friday 19 September 2008 16:12:30 Scott Lavender wrote:
> D:\P4Views\build_ProdTest\BuildSystem\production>perl -mP4 -e "print
> Can't call method "Run" on an undefined value at
> line 172.
That definitely confirms it's public depot P4Perl.
On Friday 19 September 2008 16:07:29 Scott Lavender wrote:
> Perforce - The Fast Software Configuration Management System.
> Copyright 1995-2008 Perforce Software. All rights reserved.
> Rev. P4/NTX86/2007.3/143793 (2008/01/21).
> The server is a higher patch level, but the same release:
> Server version: P4D/LINUX26X86/2007.3/152469 (2008/04/24)
> Server license: Visiprise Inc 154 users (support ends 2009/05/11)
Thanks, while the server version is not as important as the client in
instance, it's always relevant.
> I have upgraded the server to use the 2007.3 supported P4Perl. Don't
> know if you remember the dialog we had in getting my trigger scripts
> reworked. I have not done the same for the build environment.
I had forgotten - thanks for the reminder :)
OK. As a test, could you download a 2006.2 p4 client to your build
and run these commands using that instead of the 2007.3 p4.
p4 login -s # probably will say P4PASSWD invalid...
p4 login # create a new ticket
p4 tickets # you will see two tickets for the same server I
Then try running your test script again, and see if it works.
More information about the p4perl