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

Subversion fails first revision check

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • subversion-plugin
    • None
    • SuseEnterprise Linux
      JDK 1.6

      After committing a change into a Subversion repository, Jenkins jobs fail on the first Subversion revision check (see log below).
      Restarting the same job without any other Subversion commit, the revision check has no error and the job runs fine.
      After the next commit, the same error occurs.

      The Subversion server (1.6) runns on a different machine. Authentication is activated. Jenkins knows the credentials of the repo.

      I tested Subversion plugin 1.34, 1.35 and 1.37: always the same error.

      Log:

      Started by user Fischer, Lars
      Building on master in workspace
      /data/hudson_home/jobs/test.pt.prototype-parent/workspace
      Updating svn://server/test/prototype/parent
      U         pom.xml
      At revision 8512
      hudson.util.IOException2: revision check failed on
      svn://server/test/prototype/parent
             at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:170)
             at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:112)
             at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:555)
             at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:702)
             at hudson.model.AbstractProject.checkout(AbstractProject.java:1195)
             at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:576)
             at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:465)
             at hudson.model.Run.run(Run.java:1409)
             at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:481)
             at hudson.model.ResourceController.execute(ResourceController.java:88)
             at hudson.model.Executor.run(Executor.java:238)
      Caused by: org.tmatesoft.svn.core.SVNAuthenticationException: svn:
      Item is not readable
             at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:62)
             at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51)
             at org.tmatesoft.svn.core.internal.io.svn.SVNReader.handleFailureStatus(SVNReader.java:269)
             at org.tmatesoft.svn.core.internal.io.svn.SVNReader.parse(SVNReader.java:248)
             at org.tmatesoft.svn.core.internal.io.svn.SVNConnection.read(SVNConnection.java:260)
             at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.read(SVNRepositoryImpl.java:1280)
             at org.tmatesoft.svn.core.internal.io.svn.SVNRepositoryImpl.logImpl(SVNRepositoryImpl.java:835)
             at org.tmatesoft.svn.core.io.SVNRepository.log(SVNRepository.java:1034)
             at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:1027)
             at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:894)
             at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:826)
             at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:158)
             ... 10 more
      Caused by: org.tmatesoft.svn.core.SVNErrorMessage: svn: Item is not readable
             at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:200)
             at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:146)
             at org.tmatesoft.svn.core.SVNErrorMessage.create(SVNErrorMessage.java:89)
             at org.tmatesoft.svn.core.internal.io.svn.SVNReader.getErrorMessage(SVNReader.java:283)
             at org.tmatesoft.svn.core.internal.io.svn.SVNReader.handleFailureStatus(SVNReader.java:261)
             ... 19 more
      Retrying after 10 seconds
      

            recena Manuel Recena Soto
            lfischer lfischer
            Votes:
            6 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: