-
Bug
-
Resolution: Duplicate
-
Minor
-
Jenkins 2.27
Pipeline Multibranch 2.9
Subversion Plugin 2.7.1
Subversion or the multibranch plugin is reporting all changesets twice for each build. I'm guessing it accumulates the first changeset on the master node when the indexer runs to determine if a build is necessary, and then it appends the same changeset when it actually performs the svn checkout on the target node.
- is related to
-
JENKINS-37384 Changes view issues using Mercurial with Multibranch pipeline
- Open
-
JENKINS-38204 SVN plugin show all checkouts twice in pipeline project
- Resolved