[JIRA] (JENKINS-38204) SVN plugin show all checkouts twice in pipeline project

5 views
Skip to first unread message

grandemange.kevin@gmail.com (JIRA)

unread,
Sep 14, 2016, 11:35:01 AM9/14/16
to jenkinsc...@googlegroups.com
Grandemange Kevin created an issue
 
Jenkins / Bug JENKINS-38204
SVN plugin show all checkouts twice in pipeline project
Issue Type: Bug Bug
Assignee: Unassigned
Components: subversion-plugin
Created: 2016/Sep/14 3:34 PM
Environment: Jenkins 2.7.1, Linux Debian Stable, SVN plugin 2.6
Labels: svn svn-kit pipeline
Priority: Minor Minor
Reporter: Grandemange Kevin

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.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

zach.swanson@gmail.com (JIRA)

unread,
Oct 13, 2016, 9:52:01 AM10/13/16
to jenkinsc...@googlegroups.com
Zach Swanson commented on Bug JENKINS-38204
 
Re: SVN plugin show all checkouts twice in pipeline project

Actually this did occur with other SCM plugins, but they've been getting updated - see JENKINS-29326

zach.swanson@gmail.com (JIRA)

unread,
Oct 13, 2016, 9:55:02 AM10/13/16
to jenkinsc...@googlegroups.com
Zach Swanson edited a comment on Bug JENKINS-38204
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.

zach.swanson@gmail.com (JIRA)

unread,
Oct 13, 2016, 9:57:01 AM10/13/16
to jenkinsc...@googlegroups.com

zach.swanson@gmail.com (JIRA)

unread,
Oct 13, 2016, 9:57:02 AM10/13/16
to jenkinsc...@googlegroups.com
Zach Swanson edited a comment on Bug JENKINS-38204
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

mdealer@gmail.com (JIRA)

unread,
Feb 27, 2018, 3:23:02 AM2/27/18
to jenkinsc...@googlegroups.com

Any idea if this ever going to get fixed? In my case changesets get multiplied by 5 and I made sure to use 'changelog: false' wherever possible.

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

michael.kostukov@gmail.com (JIRA)

unread,
Mar 29, 2018, 9:51:04 AM3/29/18
to jenkinsc...@googlegroups.com

michael.kostukov@gmail.com (JIRA)

unread,
Mar 29, 2018, 9:51:05 AM3/29/18
to jenkinsc...@googlegroups.com
Michael Kostukov commented on Bug JENKINS-38204
 
Re: SVN plugin show all checkouts twice in pipeline project

This is REALLY getting out of hand now that I check out multiple dependencies out of SVN:

ulidtko@gmail.com (JIRA)

unread,
Apr 27, 2018, 7:35:03 AM4/27/18
to jenkinsc...@googlegroups.com
Max M commented on Bug JENKINS-38204

Looks like this is not specific to SVN.

JENKINS-29326, by the looks of it, is the very same [bunch of duplicate] issue(s), but reported with Git.

kari.jaakko.niemi@gmail.com (JIRA)

unread,
Mar 12, 2019, 3:21:04 AM3/12/19
to jenkinsc...@googlegroups.com

...another year has passed...any workaround at least, anyone?

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

brian.vandegriend@microchip.com (JIRA)

unread,
Feb 22, 2020, 11:38:03 AM2/22/20
to jenkinsc...@googlegroups.com

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.

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages