-
Bug
-
Resolution: Won't Fix
-
Minor
-
None
-
jenkins 2.7.2 LTS
linux redhat 7.2
p4-plugin 1.4.4
Hi,
Let's start with a brief introduction, after a really quick question.
I know that using 'allwrite:true' option when syncing should not be necessary.
Relying on that to have a build work hides probably some poor build design.
Ok, I admit all that
Nevertheless, thing is : I need it. (don't ask for details that I can't disclose here). Without this option part of the build chain I use breaks, and fixing it will require lots of time and efforts.
All this being said : the 'allwrite' option seem to have disappeared from the plugin configuration options.
Weird thing is : if I build a good all freestyle job using DSL to configure the plugin : 'allwrite' still works. (which is a great luck for me, to be honest)
On the other hand, in a pipeline, adding 'allwrite: true' has no effect.
So, what the is the 'official' behavior supposed to be ?
I know I can do a chmod myself after the sync in pipeline if I so wish, I really would appreciate the 'official' position to know if I treat that as a temporary workaround or as a defnitive solution as long as my build system is not fixed.
Thank you !