-
Bug
-
Resolution: Fixed
-
Major
-
Java: 1.8.0 update 66 (build 17) 64-bit
Jenkins: 1.644 (upgrade from 1.638)
Subversion plug-in: 2.5.7 (upgrade from 2.5.4)
After upgrading Jenkins, SVN checkouts started to fail. An exception is thrown during working copy revert:
org.tmatesoft.svn.core.SVNException: svn: E200030: Index not exists: I_NODES_MOVED at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:64) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:51) at org.tmatesoft.svn.core.internal.db.SVNSqlJetDb.createSqlJetError(SVNSqlJetDb.java:195) at org.tmatesoft.svn.core.internal.db.SVNSqlJetSelectStatement.openCursor(SVNSqlJetSelectStatement.java:63) at org.tmatesoft.svn.core.internal.db.SVNSqlJetStatement.next(SVNSqlJetStatement.java:90) at org.tmatesoft.svn.core.internal.db.SVNSqlJetSelectStatement.next(SVNSqlJetSelectStatement.java:108) at org.tmatesoft.svn.core.internal.wc17.db.SvnWcDbRevert.revertRecursive(SvnWcDbRevert.java:329) [complete stacktrace attached]
This seems to be triggered by Check-out Strategy being set to Use 'svn update' as much as possible, with 'svn revert' before update in project settings (which causes SVN revert to run as a result).
The origin seems to be SVNKIT-582. According to the change log, the regression seems to have been introduced in 2.5.5 with SVNKit library upgraded to 1.8.11.
Although this seems to be a known issue, I believe reporting it here can be valuable as while the original issue isn't fixed people may decide to downgrade the plug-in or plug-in developers may downgrade the library within the plug-in to the latest working version (which is...?).