Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-69418

WARNING: duplicate syncID found for pipeline jobs

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Minor Minor
    • p4-plugin

      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?

       

          [JENKINS-69418] WARNING: duplicate syncID found for pipeline jobs

          Karl Wirth added a comment -

          Hi droider - Are you polling with this workspace?

            jenkins-NODE_NAME-<PIPELINE>-<BRANCH>-EXECUTOR_NUMBER

          P4Jenkins needs fixed paths to poll against. For example if you run the job the first time you get:

           

          jenkins-slave1-pipe1-branch1-01
          View: //depot/branch1/... //jenkins-slave1-pipe1-branch1-01/...
          

           

          The highest changelist synced is 100 so we strip the variables and record Sync_ID 'jenkins-NODE_NAME-<PIPELINE>-<BRANCH>-EXECUTOR_NUMBER' with path '//depot/branch1/... //jenkins-slave1-pipe1-branch1-01/...' and latest CL '100'.

          The next time you run the job you use branch2:

           

          jenkins-slave1-pipe1-branch2-01
          View: //depot/branch2/... //jenkins-slave1-pipe2-branch1-01/...
          

           

          Because the path is different we create a different SYNC_ID with the different path.

          If you are polling against variable paths the solution is to split up the jobs to be one per path, or use multibranch instead.

          Regards,

          Karl

           

           

           

           

          Karl Wirth added a comment - Hi droider - Are you polling with this workspace?   jenkins-NODE_NAME-<PIPELINE>-<BRANCH>-EXECUTOR_NUMBER P4Jenkins needs fixed paths to poll against. For example if you run the job the first time you get:   jenkins-slave1-pipe1-branch1-01 View: //depot/branch1/... //jenkins-slave1-pipe1-branch1-01/...   The highest changelist synced is 100 so we strip the variables and record Sync_ID 'jenkins-NODE_NAME-<PIPELINE>-<BRANCH>-EXECUTOR_NUMBER' with path '//depot/branch1/... //jenkins-slave1-pipe1-branch1-01/...' and latest CL '100'. The next time you run the job you use branch2:   jenkins-slave1-pipe1-branch2-01 View: //depot/branch2/... //jenkins-slave1-pipe2-branch1-01/...   Because the path is different we create a different SYNC_ID with the different path. If you are polling against variable paths the solution is to split up the jobs to be one per path, or use multibranch instead. Regards, Karl        

            p4karl Karl Wirth
            droider Dean Wheatley
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: