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

SVN plugin show all checkouts twice in pipeline project

    XMLWordPrintable

Details

    Description

      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.

      Attachments

        Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-35176 "Tag this build" link repeated in Pipeline job with multiple svn step

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-39233 Duplicate "Tag this build" links in Pipeline

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-29326 Workflow sidebar has duplicated Git Build Data links

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Reopened

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-35176 "Tag this build" link repeated in Pipeline job with multiple svn step

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-39487 SVN changesets duplicated when using multibranch pipeline

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Activity

            Ascending order - Click to sort in descending order
            zswanson Zach Swanson added a comment - - edited

            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

            zswanson Zach Swanson added a comment - - edited 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
            gl1koz3 Edgars Batna added a comment -

            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.

            gl1koz3 Edgars Batna added a comment - 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.
            r0ll1ngst0ne Michael Kostukov added a comment -

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

            r0ll1ngst0ne Michael Kostukov added a comment - This is REALLY getting out of hand now that I check out multiple dependencies out of SVN:
            ulidtko Max M added a comment -

            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.

            ulidtko Max M added a comment - 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.
            karniemi Kari Niemi added a comment -

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

            karniemi Kari Niemi added a comment - ...another year has passed...any workaround at least, anyone?
            bvandegriend Brian Vandegriend added a comment -

            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.

            bvandegriend Brian Vandegriend added a comment - 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.
            ipilipski Ian Pilipski added a comment -

            bvandegriend, I think the work-around is to supply the changelog: false parameter on any subsequent checkout.  Seems to work for me.

             

            // first checkout
checkout(scm)

// any other checkouts
checkout(changelog: false, scm: scm)

             

            ipilipski Ian Pilipski added a comment - bvandegriend , I think the work-around is to supply the changelog: false parameter on any subsequent checkout.  Seems to work for me.   // first checkout checkout(scm) // any other checkouts checkout(changelog: false , scm: scm)  

            People

              didiez Diego Díez
              rkutic Kevin Grandemange
              Votes:
              45 Vote for this issue
              Watchers:
              40 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: