Updates on a repository with svn:externals property set fail with the following:
      AssertionError: appears to be using unpatched svnkit at jar:xxx/SVNEvent.class

      The issue is present with the latest 1.40 release.
      The issue is not preset with the 1.39 release.

          [JENKINS-13790] Subversion externals fail

          chikigai created issue -

          tapiomtr added a comment -

          We also noticed same AssertionError when Jenkins subversion pluging is upgraded from 1.39 to 1.40 version.

          tapiomtr added a comment - We also noticed same AssertionError when Jenkins subversion pluging is upgraded from 1.39 to 1.40 version.
          Martin Petzsch made changes -
          Link New: This issue is related to JENKINS-13771 [ JENKINS-13771 ]

          Tom Fanning added a comment -

          Same here. Appears to be benign - our builds still work - but we get the following message all over our logs:

          AssertionError: appears to be using unpatched svnkit at file:/C:/Users/jenkins/AppData/Local/Temp/hudson-remoting7710290003783506449/org/tmatesoft/svn/core/wc/SVNEvent.class

          Jenkins version 1.464
          Jenkins Subversion Plug-in version 1.40 (appears to be pinned, and not manually by us)

          Windows Server 2003 x86
          VisualSVN Server (SVN 1.7.1 (r1186859))

          Tom Fanning added a comment - Same here. Appears to be benign - our builds still work - but we get the following message all over our logs: AssertionError: appears to be using unpatched svnkit at file:/C:/Users/jenkins/AppData/Local/Temp/hudson-remoting7710290003783506449/org/tmatesoft/svn/core/wc/SVNEvent.class Jenkins version 1.464 Jenkins Subversion Plug-in version 1.40 (appears to be pinned, and not manually by us) Windows Server 2003 x86 VisualSVN Server (SVN 1.7.1 (r1186859))

          Kees Valkhof added a comment -

          After upgrading the SVN plugin from 1.39 -> 1.40, all externals trigger this assertion. The builds themselves succeeds. The builds use a clean checkout with client version 1.7
          Using SVN server version 1.7
          AssertionError: appears to be using unpatched svnkit at file:/C:/Users/Jenkins/AppData/Local/Temp/hudson-remoting652945517889234834/org/tmatesoft/svn/core/wc/SVNEvent.class

          Kees Valkhof added a comment - After upgrading the SVN plugin from 1.39 -> 1.40, all externals trigger this assertion. The builds themselves succeeds. The builds use a clean checkout with client version 1.7 Using SVN server version 1.7 AssertionError: appears to be using unpatched svnkit at file:/C:/Users/Jenkins/AppData/Local/Temp/hudson-remoting652945517889234834/org/tmatesoft/svn/core/wc/SVNEvent.class

          Alexander Ost added a comment -

          Same here on Linux platform.

          As a nasty side-effect, also the externals' revision information in <build directory>/revision.txt is missing. The file only contains the revision of the main repository.

          Alexander Ost added a comment - Same here on Linux platform. As a nasty side-effect, also the externals' revision information in <build directory>/revision.txt is missing. The file only contains the revision of the main repository.

          Kees Valkhof added a comment -

          We are also missing the externals revision information. Builds are also not triggered anymore on a change of an external.

          Kees Valkhof added a comment - We are also missing the externals revision information. Builds are also not triggered anymore on a change of an external.

          Markus added a comment -

          We are seeing the same issue after updating to 1.40. The job fails. This is the output:

          AssertionError: appears to be using unpatched svnkit at file:/tmp/hudson-remoting6567098393035999821/org/tmatesoft/svn/core/wc/SVNEvent.class
          At revision 5215
          AssertionError: appears to be using unpatched svnkit at file:/tmp/hudson-remoting6567098393035999821/org/tmatesoft/svn/core/wc/SVNEvent.class
          FATAL: hudson.remoting.RequestAbortedException: java.io.StreamCorruptedException: invalid type code: 41
          hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.StreamCorruptedException: invalid type code: 41
          	at hudson.remoting.Request.call(Request.java:149)
          	at hudson.remoting.Channel.call(Channel.java:646)
          	at hudson.FilePath.act(FilePath.java:821)
          	at hudson.FilePath.act(FilePath.java:814)
          	at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:743)
          	at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:685)
          	at hudson.model.AbstractProject.checkout(AbstractProject.java:1218)
          	at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:581)
          	at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:470)
          	at hudson.model.Run.run(Run.java:1434)
          	at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
          	at hudson.model.ResourceController.execute(ResourceController.java:88)
          	at hudson.model.Executor.run(Executor.java:239)
          Caused by: hudson.remoting.RequestAbortedException: java.io.StreamCorruptedException: invalid type code: 41
          	at hudson.remoting.Request.abort(Request.java:273)
          	at hudson.remoting.Channel.terminate(Channel.java:702)
          	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69)
          Caused by: java.io.StreamCorruptedException: invalid type code: 41
          	at java.io.ObjectInputStream.readObject0(Unknown Source)
          	at java.io.ObjectInputStream.readObject(Unknown Source)
          	at hudson.remoting.Command.readFrom(Command.java:90)
          	at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59)
          	at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)
          

          Markus added a comment - We are seeing the same issue after updating to 1.40. The job fails. This is the output: AssertionError: appears to be using unpatched svnkit at file:/tmp/hudson-remoting6567098393035999821/org/tmatesoft/svn/core/wc/SVNEvent.class At revision 5215 AssertionError: appears to be using unpatched svnkit at file:/tmp/hudson-remoting6567098393035999821/org/tmatesoft/svn/core/wc/SVNEvent.class FATAL: hudson.remoting.RequestAbortedException: java.io.StreamCorruptedException: invalid type code: 41 hudson.remoting.RequestAbortedException: hudson.remoting.RequestAbortedException: java.io.StreamCorruptedException: invalid type code: 41 at hudson.remoting.Request.call(Request.java:149) at hudson.remoting.Channel.call(Channel.java:646) at hudson.FilePath.act(FilePath.java:821) at hudson.FilePath.act(FilePath.java:814) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:743) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:685) at hudson.model.AbstractProject.checkout(AbstractProject.java:1218) at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:581) at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:470) at hudson.model.Run.run(Run.java:1434) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:239) Caused by: hudson.remoting.RequestAbortedException: java.io.StreamCorruptedException: invalid type code: 41 at hudson.remoting.Request.abort(Request.java:273) at hudson.remoting.Channel.terminate(Channel.java:702) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:69) Caused by: java.io.StreamCorruptedException: invalid type code: 41 at java.io.ObjectInputStream.readObject0(Unknown Source) at java.io.ObjectInputStream.readObject(Unknown Source) at hudson.remoting.Command.readFrom(Command.java:90) at hudson.remoting.ClassicCommandTransport.read(ClassicCommandTransport.java:59) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:48)

          Stephan Grimm added a comment - - edited

          I have probably the same problem and I'm getting frustrated because I really don't know how to solve it (using Jenkins 1.470, Subversion Plugin 1.40, Check-out Strategy: "Emulate clean checkout by...")

          The repository contains an external directory. Within the Main folder I changed a source file (main.c), but the changes are not updated in jobs workspace directory at the beginning of the run. Does anybody know why? Is it a bug or maybe just a wrong configuration?

          If it's a subversion plugin problem: Is there a newer version? How could I install that version?

          The log:

          Building in workspace C:\Jenkins\Config\jobs\WAP2-Trunk_DB-Build\workspace
          Cleaning up C:\Jenkins\Config\jobs\WAP2-Trunk_DB-Build\workspace\.
          Deleting C:\Jenkins\Config\jobs\WAP2-Trunk_DB-Build\workspace\BuildPlan.xml
          Deleting C:\Jenkins\Config\jobs\WAP2-Trunk_DB-Build\workspace\WLP.c
          Updating https://repos.xxx.com/svn/trunk
          U         main.c
          AssertionError: appears to be using unpatched svnkit at jar:file:/C:/Jenkins/Config/plugins/subversion/WEB-INF/lib/svnkit-1.7.4-jenkins-1.jar!/org/tmatesoft/svn/core/wc/SVNEvent.class
          At revision 11875
          At revision 11874
          no change for https://repos.xxx.com/svn/trunk since the previous build
          

          Stephan Grimm added a comment - - edited I have probably the same problem and I'm getting frustrated because I really don't know how to solve it (using Jenkins 1.470, Subversion Plugin 1.40, Check-out Strategy: "Emulate clean checkout by...") The repository contains an external directory. Within the Main folder I changed a source file (main.c), but the changes are not updated in jobs workspace directory at the beginning of the run. Does anybody know why? Is it a bug or maybe just a wrong configuration? If it's a subversion plugin problem: Is there a newer version? How could I install that version? The log: Building in workspace C:\Jenkins\Config\jobs\WAP2-Trunk_DB-Build\workspace Cleaning up C:\Jenkins\Config\jobs\WAP2-Trunk_DB-Build\workspace\. Deleting C:\Jenkins\Config\jobs\WAP2-Trunk_DB-Build\workspace\BuildPlan.xml Deleting C:\Jenkins\Config\jobs\WAP2-Trunk_DB-Build\workspace\WLP.c Updating https://repos.xxx.com/svn/trunk U main.c AssertionError: appears to be using unpatched svnkit at jar:file:/C:/Jenkins/Config/plugins/subversion/WEB-INF/lib/svnkit-1.7.4-jenkins-1.jar!/org/tmatesoft/svn/core/wc/SVNEvent.class At revision 11875 At revision 11874 no change for https://repos.xxx.com/svn/trunk since the previous build

          Markus added a comment -

          Stephan,
          We downgraded to 1.39 and it seems to have "solved" the problem. YMMV.

          Markus added a comment - Stephan, We downgraded to 1.39 and it seems to have "solved" the problem. YMMV.

            kohsuke Kohsuke Kawaguchi
            chikigai chikigai
            Votes:
            49 Vote for this issue
            Watchers:
            58 Start watching this issue

              Created:
              Updated:
              Resolved: