-
Bug
-
Resolution: Fixed
-
Blocker
-
Windows XP SP3, Windows 7
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.
- is related to
-
-
- Resolved
-
-
-
- Closed
-
[JENKINS-13790] Subversion externals fail
dlavelle
added a comment - 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
dlavelle
added a comment - 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 
tq rst
added a comment - 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.
tq rst
added a comment - 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. 
Dan Searles
added a comment - 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?
Dan Searles
added a comment - 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 issue also causes workspace cleanup failure when "Emulate clean checkout" is used. Seams to keep the old files intact.
Nick Vancauwenberghe
added a comment - 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
Nick Vancauwenberghe
added a comment - 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 
Jan Linnenkohl
added a comment - 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.
Jan Linnenkohl
added a comment - 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. 
Tom Palmer
added a comment - 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.
Tom Palmer
added a comment - 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 . 
Griffin Myers
added a comment - 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.
Griffin Myers
added a comment - 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. Code changed in jenkins
User: Tom Palmer
Path:
src/main/java/hudson/scm/SubversionSCM.java
src/main/java/hudson/scm/subversion/CheckoutUpdater.java
src/main/java/hudson/scm/subversion/SubversionUpdateEventHandler.java
src/main/java/hudson/scm/subversion/UpdateUpdater.java
http://jenkins-ci.org/commit/subversion-plugin/1e685c2e58160f8353d52ba92a6066a39f107443
Log:
[FIXED JENKINS-13790] Use the native SVNKit ISVNExternalsHandler to pick up the svn:externals URLs.
Compare: https://github.com/jenkinsci/subversion-plugin/compare/b20cf6430106...1e685c2e5816
I'm using 1.4.3, see this error still.