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

"Checksum mismatch while updating" with Subversion Plugin 1.42

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • subversion-plugin
    • None
    • sles 11, Jenkins 1.470, subversion server is CollabNet Subversion Edge 1.3.1

      After upgrading to 1.42 of the plugin, using the "Emulate clean checkout by first deleting unversioned/ignored files, then 'svn update'" svn strategy intermittently results in errors that look like the following:

      ERROR: Failed to update svn://<path>
      org.tmatesoft.svn.core.SVNException: svn: E155017: Checksum mismatch while updating '/opt/jenkins/jobs/<job>/workspace/<path to folder>/.svn/text-base/<filename>.svn-base'; expected: '151afc3b6d79443cc57fd52080d5f4d7', actual: '97acf6bf0db0d86168866633488b1a93'
      at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:85)
      at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:69)
      at org.tmatesoft.svn.core.internal.io.svn.SVNEditModeReader.driveEditor(SVNEditModeReader.java:250)
      at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.update(SVNRepositoryImpl.java:1503)
      at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.update(SVNUpdateClient16.java:557)
      at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:414)
      at org.tmatesoft.svn.core.internal.wc16.SVNUpdateClient16.doUpdate(SVNUpdateClient16.java:324)
      at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:27)
      at org.tmatesoft.svn.core.internal.wc2.old.SvnOldUpdate.run(SvnOldUpdate.java:11)
      at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:20)
      at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1221)
      at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:292)
      at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:315)
      at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:295)
      at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:391)
      at hudson.scm.subversion.UpdateUpdater$TaskImpl.perform(UpdateUpdater.java:136)
      at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:144)
      at hudson.scm.SubversionSCM$CheckOutTask.perform(SubversionSCM.java:789)
      at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:770)
      at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:753)
      at hudson.FilePath.act(FilePath.java:842)
      at hudson.FilePath.act(FilePath.java:824)
      at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:743)
      at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:685)
      at hudson.model.AbstractProject.checkout(AbstractProject.java:1242)
      at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:589)
      at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88)
      at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494)
      at hudson.model.Run.execute(Run.java:1460)
      at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
      at hudson.model.ResourceController.execute(ResourceController.java:88)
      at hudson.model.Executor.run(Executor.java:239)

      I clicked the "Downgrade to 1.39" button in the installed plugins section, restarted Jenkins and the problem appears to be solved.

      However, I notice the installed plugins section now says I have 1.34 installed, which is a little confusing.

          [JENKINS-14550] "Checksum mismatch while updating" with Subversion Plugin 1.42

          Chris Withers created issue -

          Chris Withers added a comment -

          Forgot to say, to make matters worse, when the checksum problem occurs, the Subversion Plugin doesn't fail the build, causing spurious failures in build steps later in the job.

          Chris Withers added a comment - Forgot to say, to make matters worse, when the checksum problem occurs, the Subversion Plugin doesn't fail the build, causing spurious failures in build steps later in the job.

          nealeu added a comment -

          I also get this issue with "use svn update as much as possible".

          This is a notable issue as if this happens overnight, we get builds repeated every time SVN is polled, so in our case the build server was flat out all night.

          If there is a genuine error, then I'd suggest that the plugin should fallback to doing a clean checkout anyway.

          nealeu added a comment - I also get this issue with "use svn update as much as possible". This is a notable issue as if this happens overnight, we get builds repeated every time SVN is polled, so in our case the build server was flat out all night. If there is a genuine error, then I'd suggest that the plugin should fallback to doing a clean checkout anyway.

          Code changed in jenkins
          User: Nicolas De Loof
          Path:
          src/main/java/hudson/scm/subversion/UpdateUpdater.java
          http://jenkins-ci.org/commit/subversion-plugin/a7d6b393b785bb44328302e8778d85fd7c278052
          Log:
          JENKINS-14550 switch to checkoutUpdater on corrupted workspace detection

          SCM/JIRA link daemon added a comment - Code changed in jenkins User: Nicolas De Loof Path: src/main/java/hudson/scm/subversion/UpdateUpdater.java http://jenkins-ci.org/commit/subversion-plugin/a7d6b393b785bb44328302e8778d85fd7c278052 Log: JENKINS-14550 switch to checkoutUpdater on corrupted workspace detection

          I upgraded yesterday the Subversion Plugin to 1.42 and I also get the same 'Checksum mismatch' error. Reverting to 1.39 fixes the issue.

          Alexandre Colucci added a comment - I upgraded yesterday the Subversion Plugin to 1.42 and I also get the same 'Checksum mismatch' error. Reverting to 1.39 fixes the issue.

          Chris Simmons added a comment -

          Confirmed the same behavior with v1.42. I'm attempting to downgrade to v1.41. It might be coincidence, but this only appears to happen to projects where we have renamed or removed files in SVN.

          UPDATE: v1.41 appears to have the same issue. Going to further downgrade.

          Chris Simmons added a comment - Confirmed the same behavior with v1.42. I'm attempting to downgrade to v1.41. It might be coincidence, but this only appears to happen to projects where we have renamed or removed files in SVN. UPDATE: v1.41 appears to have the same issue. Going to further downgrade.

          Chris Simmons added a comment -

          I can confirm that v1.39 appears to be the latest build that works.

          Chris Simmons added a comment - I can confirm that v1.39 appears to be the latest build that works.
          David Humeniuk made changes -
          Link New: This issue is related to JENKINS-4727 [ JENKINS-4727 ]

          This seems to be very similar to a much older issue.

          David Humeniuk added a comment - This seems to be very similar to a much older issue.

          To add to Chris Simmons' observation.

          I think it's indeed connected with renaming files. I've seen (and see) it only if the files are renamed in SVN.

          Yury Pukhalsky added a comment - To add to Chris Simmons' observation. I think it's indeed connected with renaming files. I've seen (and see) it only if the files are renamed in SVN.

            Unassigned Unassigned
            cjw296 Chris Withers
            Votes:
            27 Vote for this issue
            Watchers:
            34 Start watching this issue

              Created:
              Updated: