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

Subversion plugin fails to checkout code to workspace if the repo has empty revisions

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Major Major
    • subversion-plugin
    • None
    • Centos 5.2
      Hudson 1.355
      Subversion plugin 1.16

      Hi,

      We created a new repo in subversion using a dump and svndumpfilter on an old repo.
      The empty revisions were maintained as such for strategic reasons. The dump file had empty revisions marked with "This is an empty revision for padding" as log message and no author and no date.
      However when we create a new hudson job with the new url, it fails to checkout with a 500 error

      To repro:
      svnadmin dump oldrepo | svndumpfilter include trunk/path > dump.old
      create a new repo
      svnadmin load newrepo < dump.old

      Enter the new url in the hudson subversion repository url .
      Fails to checkout with a 500 error.

      Manual svn co works on the hudson server without any issues.

      Is there a way to actually ignore revisions if they do not have a author and a date in the subversion plugin, while calculating the log?

      Referred links
      http://hudson.361315.n4.nabble.com/Can-t-seem-to-checkout-from-SVN-1-4-5-through-http-td384856.html
      http://docs.codehaus.org/display/HAUSMATES/Could+not+access+revision+times ( Would not prefer doing this)
      https://hudson.dev.java.net/svn/hudson/trunk/hudson/plugins/subversion/src/main/java/hudson/scm/SubversionChangeLogParser.java
      https://hudson.dev.java.net/svn/hudson/trunk/hudson/plugins/subversion/src/main/java/hudson/scm/SubversionChangeLogSet.java

          [JENKINS-6561] Subversion plugin fails to checkout code to workspace if the repo has empty revisions

          I faced the same issue. It would be great to have a fix.

          We have a repository which has more that 10 years of history with revision numbers more that 180000. We had to split up the repository and the hudson checkout doesn't work since.

          As mentioned by Sathish, svn co from the command line works fine. As a workaround I am using the svn co in the execute shell. This, however does not show me the changes.

          Please provide a fix for the issue soon.

          Thanks.

          kishoresasidharan added a comment - I faced the same issue. It would be great to have a fix. We have a repository which has more that 10 years of history with revision numbers more that 180000. We had to split up the repository and the hudson checkout doesn't work since. As mentioned by Sathish, svn co from the command line works fine. As a workaround I am using the svn co in the execute shell. This, however does not show me the changes. Please provide a fix for the issue soon. Thanks.

          aggamemnon added a comment -

          This is also a serious issue for me, as we are migrating from CVS to SVN and from one combined SVN repo to many smaller ones.

          aggamemnon added a comment - This is also a serious issue for me, as we are migrating from CVS to SVN and from one combined SVN repo to many smaller ones.

            Unassigned Unassigned
            sathishsathyan sathishsathyan
            Votes:
            4 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: