P4TICKET is saved between syncs... so it should always be available. If it's not, then it means there's a bug in the plugin.
On Wednesday, 3 October 2012 10:52:56 UTC-6, Richard J wrote: > > Our Perforce server is set at security level 3 and the build scripts need > to use the P4TICKET variable to perform a checkin. > > It seems that the P4TICKET variable is only available when the plugin > tries to communicate with Perforce, fails and then does a login. > So, in order to guarantee that the variable is defined for the job, I need > to start each Jenkins jobs with a pre-SCM script that performs a Perforce > Logoff. > This is working for me, but it's ugly. > > Is there a better way? > > Richard > > >
