[p4] Scripting and ticket authentication

[Heck, Joe]

That works fine up until the point that you do something on the servers
that causes the ticket to change - then you're stuck running around and
resetting the tickets :-) 

I've used p4 login -a -p to generate a ticket that I shove into P4PASSWD
environment variable for a large number of my automated components. 

-joe

-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Jeff Grills
Sent: Tuesday, July 17, 2007 11:46 AM
To: 'Jamison, Shawn'; perforce-user at perforce.com
Subject: Re: [p4] Scripting and ticket authentication


If the machine on which you're running scripts is secure, one of the
most
effective solutions is to use a ticket that doesn't expire (or at least
won't expire for years to come).  You can change the ticket lifespan by
putting the user running the scripts in a group and setting the group's
ticket time.  Using this technique, you don't even have to have the
password
available to the script - just p4 login once, and you're set.

j


-----Original Message-----
From: perforce-user-bounces at perforce.com
[mailto:perforce-user-bounces at perforce.com] On Behalf Of Jamison, Shawn
Sent: Tuesday, July 17, 2007 1:01 PM
To: perforce-user at perforce.com
Subject: [p4] Scripting and ticket authentication


I know this has been asked before but I cant seem to find it.

Is there a way to get around the prompt for windows and unix scripts
that
need to do a p4 login?

It would be nice if I could supply a password in the script to obtain a
ticket.

Thanks
-Shawn J>

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user

_______________________________________________
perforce-user mailing list  -  perforce-user at perforce.com
http://maillist.perforce.com/mailman/listinfo/perforce-user