In pipeline projects, we checkout the code once to get the Jenkinsfile and then checkout it again one more time in the script to get the code. SVN show all the commits for the build twice in the changes of the build. This doesn't happen with other SCM plugin like git.
Actually this *did* occur with other SCM plugins, but they've been getting updated - see JENKINS-29326
In a multibranch environment this seems to be occurring when the job is allocated to the master node. The master is having to poll/checkout from subversion to get the new head revisions that trigger the jobs. Then you have to call 'checkout scm' inside the Jenkinsfile too, and apparently this causes the changeset to be recorded twice.
Actually this *did* occur with other SCM plugins, but they've been getting updated - see JENKINS-29326
In a multibranch environment this seems to be occurring when the job is allocated to the master node. The master is having to poll/checkout from subversion to get the new head revisions that trigger the jobs. Then you have to call 'checkout scm' inside the Jenkinsfile too, and apparently this causes the changeset to be recorded twice.
We're running Jenkins 2.24 with the svn-plugin at 2.6
Is there any workarounds to this issue? The build results page ends up really cluttered due to the 10+ "Tag this build" links. I would also like to see this issue resolved.