[JIRA] [subversion-plugin] (JENKINS-32515) "E200030: Index not exists: I_NODES_MOVED" while reverting working copies

155 views
Skip to first unread message

helder.magalhaes@gmail.com (JIRA)

unread,
Jan 19, 2016, 7:54:01 AM1/19/16
to jenkinsc...@googlegroups.com
Helder Magalhães created an issue
 
Jenkins / Bug JENKINS-32515
"E200030: Index not exists: I_NODES_MOVED" while reverting working copies
Issue Type: Bug Bug
Assignee: Unassigned
Attachments: E200030-IndexNotExistsI_NODES_MOVED(Stacktrace).txt
Components: subversion-plugin
Created: 19/Jan/16 12:53 PM
Environment: 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}})
Labels: regression
Priority: Major Major
Reporter: Helder Magalhães

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...?).

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

helder.magalhaes@gmail.com (JIRA)

unread,
Jan 19, 2016, 7:57:01 AM1/19/16
to jenkinsc...@googlegroups.com
Helder Magalhães updated an issue
Change By: Helder Magalhães
After upgrading Jenkins, SVN checkouts started to fail. An exception is thrown during working copy revert:

{ code noformat }

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]
{ code noformat }

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|https://issues.tmatesoft.com/issue/SVNKIT-582]. According to the [change log|https://wiki.jenkins-ci.org/display/JENKINS/Subversion+Plugin#SubversionPlugin-ChangeLog], 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|https://www.mail-archive.com/d...@wso2.org/msg50593.html], 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...?).

helder.magalhaes@gmail.com (JIRA)

unread,
Jan 19, 2016, 9:09:03 AM1/19/16
to jenkinsc...@googlegroups.com
Helder Magalhães updated an issue
Change By: Helder Magalhães
Environment: 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 }} )

scm_issue_link@java.net (JIRA)

unread,
Jan 19, 2016, 2:13:06 PM1/19/16
to jenkinsc...@googlegroups.com
SCM/JIRA link daemon commented on Bug JENKINS-32515
 
Re: "E200030: Index not exists: I_NODES_MOVED" while reverting working copies

Code changed in jenkins
User: James Nord
Path:
bin/branding.py
http://jenkins-ci.org/commit/packaging/362c47d7211b8db0883d6b85769269c30ea1e04c
Log:
[FIXED JENKINS-32515] allow specifying which variables may be blank.

It is valid for some (and only some) variables to be blank - so allow
these variables to be set to the empty string.

scm_issue_link@java.net (JIRA)

unread,
Jan 19, 2016, 2:13:06 PM1/19/16
to jenkinsc...@googlegroups.com

scm_issue_link@java.net (JIRA)

unread,
Jan 19, 2016, 2:13:06 PM1/19/16
to jenkinsc...@googlegroups.com

Code changed in jenkins
User: James Nord
Path:
bin/branding.py

[FIXED JENKINS-32515] allow specifying which variables may be blank.

Reply all
Reply to author
Forward
0 new messages