Jenkins › Jenkins issues

[JIRA] (JENKINS-13790) Subversion externals fail

Classic

List

Threaded

55 messages Options

123

JIRA noreply@jenkins-ci.org

[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

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-13790) Subversion externals fail

[ https://issues.jenkins-ci.org/browse/JENKINS-13790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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 noreply@jenkins-ci.org

[JIRA] (JENKINS-13790) Subversion externals fail

In reply to this post by JIRA noreply@jenkins-ci.org

[ https://issues.jenkins-ci.org/browse/JENKINS-13790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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))

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-13790) Subversion externals fail

In reply to this post by JIRA noreply@jenkins-ci.org

[ https://issues.jenkins-ci.org/browse/JENKINS-13790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-13790) Subversion externals fail

In reply to this post by JIRA noreply@jenkins-ci.org

[ https://issues.jenkins-ci.org/browse/JENKINS-13790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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.

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-13790) Subversion externals fail

In reply to this post by JIRA noreply@jenkins-ci.org

[ https://issues.jenkins-ci.org/browse/JENKINS-13790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163475#comment-163475 ]

Kees Valkhof commented on JENKINS-13790:
----------------------------------------

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

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-13790) Subversion externals fail

In reply to this post by JIRA noreply@jenkins-ci.org

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 noreply@jenkins-ci.org

[JIRA] (JENKINS-13790) Subversion externals fail

In reply to this post by JIRA noreply@jenkins-ci.org

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

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-13790) Subversion externals fail

In reply to this post by JIRA noreply@jenkins-ci.org

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

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

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-13790) Subversion externals fail

In reply to this post by JIRA noreply@jenkins-ci.org

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

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-13790) Subversion externals fail

In reply to this post by JIRA noreply@jenkins-ci.org

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?

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-13790) Subversion externals fail

In reply to this post by JIRA noreply@jenkins-ci.org

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-13790) Subversion externals fail

In reply to this post by JIRA noreply@jenkins-ci.org

So you don't need the subversion 1.7 working copy format?

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-13790) Subversion externals fail

In reply to this post by JIRA noreply@jenkins-ci.org

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'")

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-13790) Subversion externals fail

In reply to this post by JIRA noreply@jenkins-ci.org

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.

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-13790) Subversion externals fail

In reply to this post by JIRA noreply@jenkins-ci.org

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.

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-13790) Subversion externals fail

In reply to this post by JIRA noreply@jenkins-ci.org

It is also not triggering a build when an external changes.

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-13790) Subversion externals fail

In reply to this post by JIRA noreply@jenkins-ci.org

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

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-13790) Subversion externals fail

In reply to this post by JIRA noreply@jenkins-ci.org

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

JIRA noreply@jenkins-ci.org

[JIRA] (JENKINS-13790) Subversion externals fail

In reply to this post by JIRA noreply@jenkins-ci.org

Fixed toward 1.41.
Change By:	Kohsuke Kawaguchi (23/Jun/12 2:21 AM)
Status:	Open Resolved
Assignee:	Kohsuke Kawaguchi
Resolution:	Fixed

123