-
Bug
-
Resolution: Unresolved
-
Major
-
p4 plugin 1.10
Jenkins 2.176.1
Hello,
After updating P4 Plugin to 1.10 and Jenkins to 2.176.1 we've noticed that when jobs are sync'ing with P4SYNC step - they're running on master executor and destinated node executor at the same time. Job dissapears from master executor as soon as P4SYNC finishes.
P4SYNC step is being called within node("${label}"){} block, so it should be running exclusively on the slave with selected label (where the label is not "master").
This leads to some confusion about where the job is actually running and why exactly is it utilizing master.
Best regards,
Mateusz