[JIRA] (JENKINS-37642) SVN Checkout with external fails only after new commit

15 views
Skip to first unread message

fabian.greif@dlr.de (JIRA)

unread,
Aug 24, 2016, 3:28:01 AM8/24/16
to jenkinsc...@googlegroups.com
Fabian Greif created an issue
 
Jenkins / Bug JENKINS-37642
SVN Checkout with external fails only after new commit
Issue Type: Bug Bug
Assignee: Unassigned
Components: subversion-plugin
Created: 2016/Aug/24 7:27 AM
Environment: Jenkins 2.7.2 (recently updated from 1.6)
subversion-plugin 2.6
Priority: Blocker Blocker
Reporter: Fabian Greif

Jenkins is configured to poll for new changes in the subversion repository. The repository contains externals (with correct credentials and realm).

The jobs fails with the message below after a commit to the repository. If the build is triggered manually afterwards everything works fine. The address marked "svn.project" is repository while "svn.external" is the included external.

It appears that the checkout itself succeeded but the parsing of additional data from the external fails.

A (...)
A (...)
A (...)
U (...)

At revision 745 --> this is from svn.external

At revision 2178 --> this is from svn.project

No changes for https://svn.project since the previous build
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
hudson.util.IOException2: revision check failed on https://svn.external
at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:208)
at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:138)
at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:725)
at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:860)
at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:109)
at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:83)
at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:73)
at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:52)
at hudson.security.ACL.impersonate(ACL.java:213)
at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:49)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: org.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled
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.io.dav.http.HTTPConnection.request(HTTPConnection.java:793)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:398)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:386)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:863)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:360)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:350)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.logImpl(DAVRepository.java:1024)
at org.tmatesoft.svn.core.io.SVNRepository.log(SVNRepository.java:1038)
at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:181)
at org.tmatesoft.svn.core.internal.wc2.remote.SvnRemoteLog.run(SvnRemoteLog.java:35)
at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21)
at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1235)
at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294)
at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:968)
at org.tmatesoft.svn.core.wc.SVNLogClient.doLog(SVNLogClient.java:873)
at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:194)
... 14 more
Finished: FAILURE

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

ger.vandongen@nl.bosch.com (JIRA)

unread,
Aug 24, 2016, 5:26:01 AM8/24/16
to jenkinsc...@googlegroups.com
Ger van Dongen commented on Bug JENKINS-37642
 
Re: SVN Checkout with external fails only after new commit

This is exactly the problem I noticed, after a commit, the checkout fails only once.
Made the following work-around:
Created a "dummy" job, that only does the checkout, and let the original job be triggerd by the "dummy" job, even if that fails. This way the actual job will not fail on the checkout.

sebfere@mac.com (JIRA)

unread,
Aug 24, 2016, 5:54:04 AM8/24/16
to jenkinsc...@googlegroups.com

Same issue on one of our projects using pipeline + DSL.
We are using Jenkins 2.7.2 and we updated the pipeline plugins yesterday, and starting to get the issue.

Adding "additional credential" with the SVN realm solved the problem.

fabian.greif@dlr.de (JIRA)

unread,
Aug 24, 2016, 6:35:02 AM8/24/16
to jenkinsc...@googlegroups.com

The additional credentials don't seem to be the problem here. See https://issues.jenkins-ci.org/browse/JENKINS-31455, there it reports E200015: ISVNAuthentication provider did not provide credentials, while here the message is org.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled.

ger.vandongen@nl.bosch.com (JIRA)

unread,
Aug 24, 2016, 7:11:01 AM8/24/16
to jenkinsc...@googlegroups.com

In my case the additional credential does not solve the problem.

sebfere@mac.com (JIRA)

unread,
Aug 24, 2016, 8:35:01 AM8/24/16
to jenkinsc...@googlegroups.com
Sébastien Féré edited a comment on Bug JENKINS-37642
Same issue on one of our projects using pipeline + DSL.
We are using Jenkins 2.7.2 and we updated the pipeline plugins yesterday, and starting to get the issue.

*Adding "additional credential" with the SVN realm solved the problem.*

sean.scoggins@honeywell.com (JIRA)

unread,
Aug 24, 2016, 10:58:03 AM8/24/16
to jenkinsc...@googlegroups.com

Same problem here, using multibranch pipeline projects (freestyle projects do not seem to be affected). I have tried creating new projects (same Jenkinsfile) and get the same error. Have tried clearing cached credentials on master and slaves, same problem. Stack trace is identical to the original report. Builds consistently fail whenever there are changes in the repo. No changes in the repo leads to successful builds. All projects were building prior, so I am assuming this was introduced with a recent update of Jenkins or the plugin. Happy to provide more info or try experiments. Jenkins 2.18, Pipeline 2.2, Pipeline SCM 2.2, Subversion 2.6.

sean.scoggins@honeywell.com (JIRA)

unread,
Aug 24, 2016, 11:01:02 AM8/24/16
to jenkinsc...@googlegroups.com

Forgot to mention that I have no externals in my svn repo but see the exact same stack trace.

pengyu1104@gmail.com (JIRA)

unread,
Aug 24, 2016, 12:58:01 PM8/24/16
to jenkinsc...@googlegroups.com
Peng Yu commented on Bug JENKINS-37642

Same issue here when upgrade Pipeline: Groovy plugin 2.12 . A workaround is to downgrade Pipeline: Groovy plugin to 2.11.

sean.scoggins@honeywell.com (JIRA)

unread,
Aug 24, 2016, 1:43:01 PM8/24/16
to jenkinsc...@googlegroups.com

Downgrading Jenkins to 2.17 from 2.18 seems to have resolved this for me. I have Jenkins 2.17, Pipeline: Groovy 2.12, Subversion 2.6, Pipeline: SCM 2.2.

ifernandezcalvo@cloudbees.com (JIRA)

unread,
Apr 18, 2018, 5:42:02 AM4/18/18
to jenkinsc...@googlegroups.com
Ivan Fernandez Calvo closed an issue as Duplicate
 
Change By: Ivan Fernandez Calvo
Status: Open Closed
Resolution: Duplicate
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages