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

Workspace not automatically reset when detecting a changed repository

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Cannot Reproduce
    • Icon: Minor Minor
    • subversion-plugin
    • None
    • Debian Linux.
      svnsync, svnadmin version 1.5.1 (for maintaining the repository)
      Hudson 1.339.

      For performance reasons (slow and unrelieable) network and many jobs against the same subversion repositories, I run the builds against a mirror repository that is updated every ten minutes by another hudson job. When I accidentally destroyed the mirror and recreated it, I assumed that Hudson would detect that change, delete the entire workspace, check out, and build.

      What happened was that Hudson refused to build. The following error is found in the console log for several consecutive build attempts:
      ========
      Updating file:///home/argonightly/REPOS/argouml.tigris.org/svn/argouml/trunk/src
      ERROR: Failed to update file:///home/argonightly/REPOS/argouml.tigris.org/svn/argouml/trunk/src
      org.tmatesoft.svn.core.SVNException: svn: Repository UUID '2908db52-8556-460b-b728-5e4d430d9275' doesn't match expected UUID '6c77ef4e-2a1d-4a20-ac29-281c6bae4446'
      at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64)
      at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
      at org.tmatesoft.svn.core.wc.SVNBasicClient.createRepository(SVNBasicClient.java:347)
      at org.tmatesoft.svn.core.wc.SVNBasicClient.createRepository(SVNBasicClient.java:330)
      at org.tmatesoft.svn.core.wc.SVNUpdateClient.update(SVNUpdateClient.java:535)
      at org.tmatesoft.svn.core.wc.SVNUpdateClient.doUpdate(SVNUpdateClient.java:401)
      at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:634)
      at hudson.scm.SubversionSCM$CheckOutTask.invoke(SubversionSCM.java:595)
      at hudson.FilePath.act(FilePath.java:676)
      at hudson.FilePath.act(FilePath.java:660)
      at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:588)
      at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:536)
      at hudson.model.AbstractProject.checkout(AbstractProject.java:1013)
      at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:486)
      at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:412)
      at hudson.model.Run.run(Run.java:1179)
      at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
      at hudson.model.ResourceController.execute(ResourceController.java:88)
      at hudson.model.Executor.run(Executor.java:122)
      Recording test results
      =========

      The problem is solved by manually wiping out the workspace and rebuilding.

      I would like the Subversion within Hudson to detect this problem and erase the workspace and start over in the same way as on detection of other fundamental subversion inconsistencies.

            Unassigned Unassigned
            linustolke Linus Tolke
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: