-
New Feature
-
Resolution: Unresolved
-
Minor
My Jenkins instance System log (<HOST>/manage/log/all) is full of the following logs:
PM SEVERE org.jenkinsci.plugins.p4.tagging.TagAction getLastChange
WARNING: duplicate syncID found: jenkins-NODE_NAME-<PIPELINE>-<BRANCH>-EXECUTOR_NUMBER
Can you advise how to avoid them for Jenkins pipelines?
In the pipeline configuration, a single Perforce / Helix path, a single path is entered under "Include branches:"
The "populate options" is set to "Auto cleanup and sync".
In the sub-pipeline (branch) configuration, the Build Trigger is set to "Poll SCM".
Does the WARNING get logged if the workspace already exists on the build node due to a prior run?