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

pipeline checkout scm duplicated changeset (perforce)


      Solution: For anyone getting a similar issue, this is a solution:

      checkout scm: scm, poll: false, changelog: false

      Problem: Same as JENKINS-40352(which is for GIT)

      Using 

      checkout scm

      checkout scm is done at:

      pipeline Jenkinsfile script checkout

      pipeline checkout after loading the Jenkinsfile (to get full depot)

      checkout scm after cleanWs() (if requested as a parameter in the build)

          [JENKINS-72013] pipeline checkout scm duplicated changeset (perforce)

          Eivind added a comment - - edited

          I am having the same issue. Is there some parameter one can pass to the node/stage e.g.

          options {
              scmDontGenerateChangeSummary()
          }
          

          That allows one to skip tracking the changes (or perhaps the summary of changes to generated on the built-in node?).

          Eivind added a comment - - edited I am having the same issue. Is there some parameter one can pass to the node/stage e.g. options { scmDontGenerateChangeSummary() } That allows one to skip tracking the changes (or perhaps the summary of changes to generated on the built-in node?).

          Eivind added a comment -

          Also to add, it seems like I am seeing these warnings in the logs:

          WARNING: duplicate syncID found: jenkins-NODE_NAME-PROJECT-BRANCH-EXECUTOR_NUMBER
          Found last change xxxxxxx on syncID jenkins-NODE_NAME-PROJECT-BRANCH-EXECUTOR_NUMBER
          Found last change xxxxxxx on syncID jenkins-NODE_NAME-PROJECT-BRANCH-EXECUTOR_NUMBER
          

          Eivind added a comment - Also to add, it seems like I am seeing these warnings in the logs: WARNING: duplicate syncID found: jenkins-NODE_NAME-PROJECT-BRANCH-EXECUTOR_NUMBER Found last change xxxxxxx on syncID jenkins-NODE_NAME-PROJECT-BRANCH-EXECUTOR_NUMBER Found last change xxxxxxx on syncID jenkins-NODE_NAME-PROJECT-BRANCH-EXECUTOR_NUMBER

          Danilo added a comment - - edited

          After a long search, this is the solution I am using:

          checkout scm: scm, poll: false, changelog: false

           

          Danilo added a comment - - edited After a long search, this is the solution I am using: checkout scm: scm, poll: false , changelog: false  

          Eivind added a comment -

          I just figured that out before I read your reply. Thank you for the update. 

           

          Now I have to figure out how to do a p4 unshelve if env.P4_REVIEW is set in the environment. 

          Eivind added a comment - I just figured that out before I read your reply. Thank you for the update.    Now I have to figure out how to do a p4 unshelve if env.P4_REVIEW is set in the environment. 

          Eivind added a comment -

          Should the bug be closed then?

          Eivind added a comment - Should the bug be closed then?

            Unassigned Unassigned
            dramoz Danilo
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: