-
Type:
Bug
-
Resolution: Not A Defect
-
Priority:
Major
-
Component/s: p4-plugin
-
None
-
Environment:Server version: P4D/LINUX26X86_64/2016.1/1454320 (2016/10/19)
Server license: AB Initio Software LLC 281 users (support ends 2022/05/15)
jenkins using p4-plugin in freestyle, maven, and pipeline jobs
Jenkins 2.319.3
p4-plugin 1.12.2
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?
