Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Not A Defect
-
None
Description
our jenkins jobs run as a 'build' user with an nfs mounted home dir
the change of the p4-plugin to start using 'p4 login -a' (we see with 1.12.2) is constantly rewriting the /u/build/.p4tickets files
this causes a LOT of spurious build failures as two jobs conflict and the .p4tickets is not available and a the build will fail out during the SCM step with
Perforce password (P4PASSWD) invalid or unset.
I know we can work around this by backing the plugin to 1.11.6 but then we lose any new features.
Is there any good reason for using 'p4 login -a' rather than 'p4 login -a -p' to avoid the constant file rewrite?
Attachments
Activity
Hi Karl,
my Jenkins credentials window does NOT include an 'Enable User Sesssion' option, I have a much smaller set of options. Is this an updated credentials plugin?
I can see Credentials Binding Plugin 1.27.1, Credentials Plugin 1074.v60e6c29b_b_44b_
what version of the credentials plugin provides this.
and it's not the 'p4 login -s' that the issue, it's the 'p4 login -a ' that seems to be re-writting the P4TICKETS file.
Karl Wirth
added a comment - Hi Heather,
It's the new Perforce plugin 1.12.2 that should provide that advanced option. (sorry forgot to mention its under advanced). The reason I am asking is if it;s ticked it should reduce the amount of access to the .p4tickets file by using an in memory cache.
If you still dont see it please try creating a new Perforce credential then click 'Advanced'.
Regards,
Karl
Karl Wirth
added a comment - Hi Heather,
It's the new Perforce plugin 1.12.2 that should provide that advanced option. (sorry forgot to mention its under advanced). The reason I am asking is if it;s ticked it should reduce the amount of access to the .p4tickets file by using an in memory cache.
If you still dont see it please try creating a new Perforce credential then click 'Advanced'.
Regards,
Karl ah, we've backed the p4 plugin back to 1.11.6 to avoid the problem as it was severely impacting develops even trying to run local builds due to contention for reading/updating the nfs mounted P4TICKETS file. I have a test instance I can put the newer plugin into and check it's default settings.
I confirmed that with p4-plugin 1.12.2 I have the option to set the enable user session and will try it out on my test instance,
Hi abinitio_user
Is 'Enable user session' switched on for the credential? Does toggling that help?