[JIRA] (JENKINS-13790) Subversion externals fail
SCM/JIRA link daemon resolved JENKINS-13790 as Fixed Subversion externals fail Change By: SCM/JIRA link daemon (04/Jan/13 8:41 AM) Status: InProgress Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Griffin Myers commented on JENKINS-13790 Subversion externals fail Many thanks to Tom Palmer for his fix. I've manually built the SVN plugin with his mods (followed instructions here: https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial#Plugintutorial-BuildingaPlugin) and svn:externals polling functionality seems to be restored. I've tested this with multiple Jenkins projects with wc 1.7 with many, many directory externals without any issues. The only thing I haven't tested are file externals, which I know were also problematic with recent official releases of the plugin. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Tom Palmer commented on JENKINS-13790 Subversion externals fail I have a fix for this within my fork of the plugin on github. It uses the native support within SVNKit to determine the URLs for the svn:externals that the project contains. Because it natively hooks into SVNKit it works regardless of the SVN version you wish to use in your working copies. The pull request is https://github.com/jenkinsci/subversion-plugin/pull/30. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Nick Vancauwenberghe commented on JENKINS-13790 Subversion externals fail I hit... AssertionError: appears to be using unpatched svnkit at jar:file:/D:/Jenkins/plugins/subversion/WEB-INF/lib/svnkit-1.7.4-jenkins-3.jar!/org/tmatesoft/svn/core/wc/SVNEvent.class This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Jan Linnenkohl commented on JENKINS-13790 Subversion externals fail Hi Nick, the problem is, that the "patched" svnkit is already in use, but the "patches" for subversion 1.7 are still missing. May be you could write to the mailing list, because here seems none of the plugin developers to listen. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
aleksas commented on JENKINS-13790 Subversion externals fail This issue also causes workspace cleanup failure when "Emulate clean checkout" is used. Seams to keep the old files intact. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Dan Searles commented on JENKINS-13790 Subversion externals fail Oct 29 there was a new svnkit released which mentions it is fixed for SVN 1.7 server and working directories Will there be a Jenkins upgrade soon that uses the latest svnkit? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
tq rst commented on JENKINS-13790 Subversion externals fail Seeing the same error in my build logs for 1.486, but the error doesn't appear to be fatal. The rest of the repo checks out properly and the build works fine. 14:43:45 AssertionError: appears to be using unpatched svnkit at file:/tmp/hudson-remoting4395012546022522440/org/tmatesoft/svn/core/wc/SVNEvent.class This is with svn 1.7. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
rattapon sattayarat commented on JENKINS-13790 Subversion externals fail I'm using 1.4.3, see this error still. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
dlavelle commented on JENKINS-13790 Subversion externals fail Rattapon, You may have to revert your plugin back to the previous version and also make sure you are using Subversion 1.6 working copy format(main settings). then you also must start with a fresh workspace for the Jenkins job so a fresh checkout is made. Have you done this? -Dewayne This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Jan Linnenkohl commented on JENKINS-13790 Subversion externals fail I just have the checked the sources and found out, that only the wc16 is supported for the externals. There is a missing support for wc17. So in an old project, where still the working copy was in format 16, I was able to update. Using a fresh checkout it generates version 17 and the externals fail. So there is a need to update the patched svnkit to support the new working copy format. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Jan Linnenkohl commented on JENKINS-13790 Subversion externals fail I went now back to use subversion 1.6 working copy format (main settings) and it works fine. Be sure that you delete the existing working copies rerun the builds. Otherwise it keep using the 1.7 working copy. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
dlavelle commented on JENKINS-13790 Subversion externals fail Jan, This is exactly what I had to do as well. Our instance is running as expected now. -Dewayne This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Kyle Wiering commented on JENKINS-13790 Subversion externals fail (Context: Windows server/slave - AssertionError: appears to be using unpatched svnkit) Ran into this same/similar problem locally. On the slave machine there was a second svn.exe located in a different path (sliksvn client). It was an older version of svn.exe and caused this exact error message. Just to 'cover the bases' you can type svn --version in the command line on the slave. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Stephan Grimm commented on JENKINS-13790 Subversion externals fail How can we increase the priority of fixing this bug? In my opinion it is an important bug-fix, because at the moment we have to always check out a fresh copy of our svn repository to be sure the working directory is up to date. And this takes (too) much time and leads to (too) much traffic on the server. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Stephan Grimm commented on JENKINS-13790 Subversion externals fail Is there any activity on this issue? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Milos Svasek edited a comment on JENKINS-13790 Subversion externals fail Update to use SVNKit version 1.7.5 may help with the externals issue, because there are some fixies about the svn:externals. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Jan Linnenkohl updated JENKINS-13790 Subversion externals fail We are also working with a lot of externals in our projects. And they still not working in 1.4.2 / 1.446.1 (configured to use workspace 1.7). How can we help, to find a resolution for this problem? Change By: Jan Linnenkohl (31/Jul/12 3:35 PM) Priority: Major Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Jan Linnenkohl updated JENKINS-13790 Subversion externals fail Change By: Jan Linnenkohl (31/Jul/12 4:02 PM) Fix Version/s: current This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Sarah Woodall commented on JENKINS-13790 Subversion externals fail I am also seeing this problem. I have just installed the latest Jenkins (now 1.474) on a brand-new Windows machine. The plugin manager in Jenkins told me that the Subversion plugin was out of date (it was version 1.39), so I updated it to the latest one (1.42) before starting to set up my builds. These same builds had worked fine on a different Windows machine, which was running Jenkins 1.441 with version 1.34 of the Subversion plugin. When my builds checked their sources out of Subversion I got this message: AssertionError: appears to be using unpatched svnkit at jar:file:/Q:/jenkins/plugins/subversion/WEB-INF/lib/svnkit-1.7.4-jenkins-3.jar!/org/tmatesoft/svn/core/wc/SVNEvent.class These builds are performed entirely on the (Windows) master, not on any slaves. Our repositories use svn externals, so I assume I am seeing the same problem that others have reported here. I am having trouble going back to version 1.39 of the Subversion plugin, because of the incompatibility in working copy layout between svn 1.6 and 1.7 (I have also installed TortoiseSVN and the command-line svn client, and I want to use Subversion 1.7 for everything on this new machine). I would really appreciate a fix for this bug so that I can use a version of the plugin that is compatible with svn 1.7. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Sarah Woodall updated JENKINS-13790 Subversion externals fail Change By: Sarah Woodall (16/Jul/12 3:51 PM) Status: Reopened Open This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Sarah Woodall started work on JENKINS-13790 Subversion externals fail Change By: Sarah Woodall (16/Jul/12 3:51 PM) Status: Open InProgress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Sarah Woodall edited a comment on JENKINS-13790 Subversion externals fail I am also seeing this problem. I have just installed the latest Jenkins (now 1.474) on a brand-new Windows 7 machine. The plugin manager in Jenkins told me that the Subversion plugin was out of date (it was version 1.39), so I updated it to the latest one (1.42) before starting to set up my builds. These same builds had worked fine on a different Windows 7 machine, which was running Jenkins 1.441 with version 1.34 of the Subversion plugin. When my builds checked their sources out of Subversion I got this message: AssertionError: appears to be using unpatched svnkit at jar:file:/Q:/jenkins/plugins/subversion/WEB-INF/lib/svnkit-1.7.4-jenkins-3.jar!/org/tmatesoft/svn/core/wc/SVNEvent.class These builds are performed entirely on the (Windows) master, not on any slaves. Our repositories use svn externals, so I assume I am seeing the same problem that others have reported here. I am having trouble going back to version 1.39 of the Subversion plugin, because of the incompatibility in working copy layout between svn 1.6 and 1.7 (I have also installed TortoiseSVN and the command-line svn client, and I want to use Subversion 1.7 for everything on this new machine). I would really appreciate a fix for this bug so that I can use a version of the plugin that is compatible with svn 1.7. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Jay Beeckman commented on JENKINS-13790 Subversion externals fail Can we get an update on this? It has twice caused me to load the plugin, upgrade my workspaces, and have to revert them back because it doesn't work properly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
jonnydee commented on JENKINS-13790 Subversion externals fail I can confirm this issue with 1.42, too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
chikigai reopened JENKINS-13790 Subversion externals fail A number of users are still experiencing the AssertionError. Change By: chikigai (26/Jun/12 7:52 AM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
chikigai commented on JENKINS-13790 Subversion externals fail Issue is still present with 1.42. File/Folder externals are updated correctly but are always coupled with the same following error: AssertionError: appears to be using unpatched svnkit at jar:xxx/SVNEvent.class This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
SCM/JIRA link daemon commented on JENKINS-13790 Subversion externals fail Code changed in jenkins User: Kohsuke Kawaguchi Path: svnkit/src/main/java/org/tmatesoft/svn/core/internal/wc16/SVNUpdateClient16.java http://jenkins-ci.org/commit/svnkit/bfddf2421bd7d148fad628471dd6d19ee40cd759 Log: JENKINS-13790 Added svn:externals information to callback This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
SCM/JIRA link daemon commented on JENKINS-13790 Subversion externals fail Code changed in jenkins User: Kohsuke Kawaguchi Path: pom.xml http://jenkins-ci.org/commit/subversion-plugin/79cdc08cfd7baa77cce4fdda7134c0b898cea7f1 Log: Pick up fix for JENKINS-13790 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Kohsuke Kawaguchi resolved JENKINS-13790 as Fixed Subversion externals fail Fixed toward 1.41. Change By: Kohsuke Kawaguchi (23/Jun/12 2:21 AM) Status: Open Resolved Assignee: KohsukeKawaguchi Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Markus Hjerto
commented on JENKINS-13790
Subversion externals fail
No we don't need subversion 1.7. We upgraded because of a another problem ("org.tmatesoft.svn.core.SVNException: svn: REPORT /seesaw/!svn/vcc/default failed", "Checksum mismatch while updating '/jenkins-directory/products/run/.svn/text-base/RUN_ALL.svn-base'; expected: '6d28a7249c635f15621f5f5ac5fa28d2', actual: 'null'")
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Kohsuke Kawaguchi commented on JENKINS-13790 Subversion externals fail It looks like the build has happened on a slave, can you tell us about how this slave is connected? SSH, Java Web Start, etc. If you are not sure, just let us know the name of the slave and attach $JENKINS_HOME/config.xml. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Florian Doersch commented on JENKINS-13790 Subversion externals fail We have the same problem with 0.40. I don't think its dependent on how the slaves are connected. Our Linux Slaves are connected via SSH and our windows slaves via DCOM/Windows Service. Both slave-types get that error on 1.6 subversion format. We reverted back to 0.39 too now to get it working again. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Jay Beeckman commented on JENKINS-13790 Subversion externals fail It is also not triggering a build when an external changes. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Stephan Grimm edited a comment on JENKINS-13790 Subversion externals fail Because of some build scripts we need the subversion 1.7 working copy format. as I know, the version 1.39 of the subversion plugin does use the 1.6 working copy format. is someone working on a solution? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Stephan Grimm commented on JENKINS-13790 Subversion externals fail 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) 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 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Stephan Grimm edited a comment on JENKINS-13790 Subversion externals fail 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 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Markus Hjerto commented on JENKINS-13790 Subversion externals fail Stephan, We downgraded to 1.39 and it seems to have "solved" the problem. YMMV. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Stephan Grimm commented on JENKINS-13790 Subversion externals fail Because of some build scripts we need the subversion 1.7 working copy format. as I know, the version 1.39 of the subversion plugin does use the 1.6 working copy format. is someone working on a solution? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
Markus Hjerto commented on JENKINS-13790 Subversion externals fail 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) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
[ https://issues.jenkins-ci.org/browse/JENKINS-13790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163313#comment-163313 ] Alexander Ost commented on JENKINS-13790: - 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. Subversion externals fail - Key: JENKINS-13790 URL: https://issues.jenkins-ci.org/browse/JENKINS-13790 Project: Jenkins Issue Type: Bug Components: subversion Affects Versions: current Environment: Windows XP SP3 Reporter: chikigai 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
[ https://issues.jenkins-ci.org/browse/JENKINS-13790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163156#comment-163156 ] Kees Valkhof commented on JENKINS-13790: 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 Subversion externals fail - Key: JENKINS-13790 URL: https://issues.jenkins-ci.org/browse/JENKINS-13790 Project: Jenkins Issue Type: Bug Components: subversion Affects Versions: current Environment: Windows XP SP3 Reporter: chikigai 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
[ https://issues.jenkins-ci.org/browse/JENKINS-13790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=163001#comment-163001 ] Tom Fanning commented on JENKINS-13790: --- 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)) Subversion externals fail - Key: JENKINS-13790 URL: https://issues.jenkins-ci.org/browse/JENKINS-13790 Project: Jenkins Issue Type: Bug Components: subversion Affects Versions: current Environment: Windows XP SP3 Reporter: chikigai 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
[ https://issues.jenkins-ci.org/browse/JENKINS-13790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162816#comment-162816 ] tapiomtr commented on JENKINS-13790: We also noticed same AssertionError when Jenkins subversion pluging is upgraded from 1.39 to 1.40 version. Subversion externals fail - Key: JENKINS-13790 URL: https://issues.jenkins-ci.org/browse/JENKINS-13790 Project: Jenkins Issue Type: Bug Components: subversion Affects Versions: current Environment: Windows XP SP3 Reporter: chikigai 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13790) Subversion externals fail
chikigai created JENKINS-13790: -- Summary: Subversion externals fail Key: JENKINS-13790 URL: https://issues.jenkins-ci.org/browse/JENKINS-13790 Project: Jenkins Issue Type: Bug Components: subversion Affects Versions: current Environment: Windows XP SP3 Reporter: chikigai 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. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
