-
Bug
-
Resolution: Fixed
-
Minor
-
Jenkins 2.7.1, Linux Debian Stable, SVN plugin 2.6
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.
- is duplicated by
-
JENKINS-35176 "Tag this build" link repeated in Pipeline job with multiple svn step
-
- Resolved
-
- is related to
-
JENKINS-39233 Duplicate "Tag this build" links in Pipeline
-
- Open
-
-
JENKINS-29326 Workflow sidebar has duplicated Git Build Data links
-
- Reopened
-
-
JENKINS-35176 "Tag this build" link repeated in Pipeline job with multiple svn step
-
- Resolved
-
-
JENKINS-39487 SVN changesets duplicated when using multibranch pipeline
-
- Resolved
-
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