• Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Critical Critical
    • subversion-plugin
    • None

      We are using a multi-branch-pipeline which does polling against subversion. The Jenkinsfile is located at a separate directory so we need to do a separate checkout step to get the real project files.

      That checkout step fails in the scripted pipeline with an Exception: 

      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:70)
      	at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:57)
      	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:760)
      	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:352)
      	at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:340)
      	at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:897)
      	at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:363)
      	at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:353)
      	at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.logImpl(DAVRepository.java:1003)
      	at org.tmatesoft.svn.core.io.SVNRepository.log(SVNRepository.java:1041)
      	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:1239)
      	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:190)
      Caused: hudson.util.IOException2: revision check failed on https://xxx/xxx
      	at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:204)
      	at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:124)
      	at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:757)
      	at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:898)
      	at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:113)
      	at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:85)
      	at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:75)
      	at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47)
      	at hudson.security.ACL.impersonate(ACL.java:290)
      	at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)
      	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:1149)
      	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
      	at java.lang.Thread.run(Thread.java:748)
      
      

      Previously this was hidden by the NPE which was solved by --JENKINS-51817--.

          [JENKINS-51979] subversion checkout fails with SAXException

          Could you provide more details about the environment? 

          • Which Jenkins Core?
          • Which Subversion Plugin version?
          • Has the repo externals?
          • Do you use different credentials for each repo?
          • Could you provide a snippet of the Jenkins file?
          • Could you provide the config.xml of the job?
          • Do it happens with all repos?
          • Could you use other protocol http/svn?
          • Do you use a proxy to connect to the repo? if so, Could you connect directly?

           

          Ivan Fernandez Calvo added a comment - Could you provide more details about the environment?  Which Jenkins Core? Which Subversion Plugin version? Has the repo externals? Do you use different credentials for each repo? Could you provide a snippet of the Jenkins file? Could you provide the config.xml of the job? Do it happens with all repos? Could you use other protocol http/svn? Do you use a proxy to connect to the repo? if so, Could you connect directly?  

          • Jenkins 2.121.1
          • Suversion Plugin 2.11.0
          • No externals
          • No different credentials
          • Only using https (direct, no proxy)

          Jenkinsfile and config.xml are a little more of a problem. Basically I assume some weird classpath issue cause the only possible cause would be if creating the changelog in DirAwareSVNXMLLogHandler fails when adding a tag.

           

           

          Dietmar Scheidl added a comment - Jenkins 2.121.1 Suversion Plugin 2.11.0 No externals No different credentials Only using https (direct, no proxy) Jenkinsfile and config.xml are a little more of a problem. Basically I assume some weird classpath issue cause the only possible cause would be if creating the changelog in DirAwareSVNXMLLogHandler fails when adding a tag.    

          Short description of our directory structure:

          \_ trunk | branches/...
            \_ common
            \_ product
              \_ sources
              | \_ ...
              \_ pipeline
                \_ build
                | \_ Jenkinsfile
                \_ library
                  \_ vars
                    \_ someused.groovy

           

          In Jenkins there is an folder which defines the "pipeline-library". A job (e.g. build) is located in that folder. Both point to the root of the svn tree. The includeded branches looks like "trunk/product/pipeline/build,branches/*/product/build". This yields a multi-branch-pipeline project which uses also the associated library for that branch.

          A simplified Jenkinsfile (e.g. build) looks like:

          branch = env.BRANCH_NAME - 'product/pipeline/build'
          library "pipeline-library@${branch}/product/pipeline/library"
          
          scmCommon = [credentialsId: scm.locations[0].credentialsId, local: 'common', remote: "https://xxx/${branch}/common"]
          scmProduct = [credentialsId: scm.locations[0].credentialsId, local: 'product', remote: "https://xxx/${branch}/product"]
          
          scmAll = [
            scmCommon,
            scmProduct
          ]
          
          stage('record-changes') {
            node('pipeline') {
              def scmVars = checkout scm: [
                $class: 'SubversionSCM', 
                locations: scmAll, 
                workspaceUpdater: [
                 $class: 'UpdateUpdater'
                ]
              ]
          
              // ...
            }
          }
          
          ...

          That checkout to record the changes already fails.

          Later stages do more specific checkouts to build several parts on different nodes in parallel. To have a consolidated change log, I am doing one dummy checkout of everything upfront.

          Dietmar Scheidl added a comment - Short description of our directory structure: \_ trunk | branches/... \_ common \_ product \_ sources | \_ ... \_ pipeline \_ build | \_ Jenkinsfile \_ library \_ vars \_ someused.groovy   In Jenkins there is an folder which defines the "pipeline-library". A job (e.g. build) is located in that folder. Both point to the root of the svn tree. The includeded branches looks like "trunk/product/pipeline/build,branches/*/product/build". This yields a multi-branch-pipeline project which uses also the associated library for that branch. A simplified Jenkinsfile (e.g. build) looks like: branch = env.BRANCH_NAME - 'product/pipeline/build' library "pipeline-library@${branch}/product/pipeline/library" scmCommon = [credentialsId: scm.locations[0].credentialsId, local: 'common' , remote: "https: //xxx/${branch}/common" ] scmProduct = [credentialsId: scm.locations[0].credentialsId, local: 'product' , remote: "https: //xxx/${branch}/product" ] scmAll = [ scmCommon, scmProduct ] stage( 'record-changes' ) { node( 'pipeline' ) { def scmVars = checkout scm: [ $class: 'SubversionSCM' , locations: scmAll, workspaceUpdater: [ $class: 'UpdateUpdater' ] ] // ... } } ... That checkout to record the changes already fails. Later stages do more specific checkouts to build several parts on different nodes in parallel. To have a consolidated change log, I am doing one dummy checkout of everything upfront.

          Ivan Fernandez Calvo added a comment - - edited

          Could you execute this groovy code in the Script console? this will change the logHandler in the point that it fails for a simpler one, then make a try to see if we have more details on logs. https://github.com/jenkinsci/subversion-plugin/blob/master/src/main/java/hudson/scm/SubversionChangeLogBuilder.java#L190

           

           

          println hudson.scm.SubversionChangeLogBuilder.debug
          hudson.scm.SubversionChangeLogBuilder.debug = true
          println hudson.scm.SubversionChangeLogBuilder.debug

          Ivan Fernandez Calvo added a comment - - edited Could you execute this groovy code in the Script console? this will change the logHandler in the point that it fails for a simpler one, then make a try to see if we have more details on logs. https://github.com/jenkinsci/subversion-plugin/blob/master/src/main/java/hudson/scm/SubversionChangeLogBuilder.java#L190     println hudson.scm.SubversionChangeLogBuilder.debug hudson.scm.SubversionChangeLogBuilder.debug = true println hudson.scm.SubversionChangeLogBuilder.debug

          I have rolled back to a state known working to get our product system running. I reverted to my own compiled version which has the fix from Bernd included. Also removed one other plugin which was introduced in the process of updating (statistics-gatherer-plugin) but was no trouble in our staging env. I can try to reproduce again hopefully on weekend when there is no load on the production env.

          Dietmar Scheidl added a comment - I have rolled back to a state known working to get our product system running. I reverted to my own compiled version which has the fix from Bernd included. Also removed one other plugin which was introduced in the process of updating (statistics-gatherer-plugin) but was no trouble in our staging env. I can try to reproduce again hopefully on weekend when there is no load on the production env.

          Dietmar Scheidl added a comment - - edited

          Sadly happend again ... I only added a space to one of the files and commited that change ... the log recorded the change but it seems creating the changelog.xml failed somehow.

          Started by an SCM change
          Opening connection to https://xxx/
          Checking out svn https://xxx/trunk/product/pipeline/build into /var/lib/jenkins/workspace/_trunk_product_pipeline_build-...@script to read Jenkinsfile
          Updating https://xxx/trunk/product/pipeline/build@795111 at revision 795111
          Using sole credentials ******/****** (******) in realm ‘<https://xxx:443> Subversion Software Development repository’
          At revision 795111
          ...
          No changes for https://xxx/trunk/product/pipeline/build since the previous build
          Running in Durability level: MAX_SURVIVABILITY
          [Pipeline] properties
          [Pipeline] library
          Loading library pipeline-library@trunk/product/pipeline/library
          Opening connection to https://xxx/
          Updating https://xxx/trunk/product/pipeline/library@795111 at revision 795111
          Using sole credentials ******/****** (******) in realm ‘<https://xxx:443> Subversion Software Development repository’
          At revision 795111
          
          No changes for https://xxx/trunk/product/pipeline/library since the previous build
          [Pipeline] timestamps
          [Pipeline] {
          [Pipeline] stage
          [Pipeline] { (init)
          [Pipeline] node
          20180621-195613 Agent k8s-pipeline-mnj1s is provisioned from template Kubernetes Pod Template
          20180621-195613 Agent specification [Kubernetes Pod Template] (pipeline): 
          20180621-195613 * [jnlp] docker-registry/library/someimage:latest(resourceRequestCpu: , resourceRequestMemory: , resourceLimitCpu: , resourceLimitMemory: )
          20180621-195613 
          20180621-195613 Running on k8s-pipeline-mnj1s in /home/jenkins/workspace/_trunk_product_pipeline_build-...
          [Pipeline] {
          [Pipeline] checkout
          20180621-195613 Updating https://xxx/trunk/common at revision '2018-06-21T17:56:10.538 +0000'
          20180621-195613 Using sole credentials ******/****** (******) in realm ‘<https://xxx:443> Subversion Software Development repository’
          20180621-195613 At revision 795111
          20180621-195613 
          20180621-195614 Updating https://xxx/trunk/product at revision '2018-06-21T17:56:10.538 +0000'
          20180621-195614 Using sole credentials ******/****** (******) in realm ‘<https://xxx:443> Subversion Software Development repository’
          20180621-195615 U ...
          20180621-195623 At revision 795111
          20180621-195623 
          20180621-195624 No changes for https://xxx/trunk/common since the previous build
          20180621-195624 Computing changelog of https://xxx/trunk/product from 795111 to 795111
          20180621-195624 Using sole credentials ******/****** (******) in realm ‘<https://xxx:443> Subversion Software Development repository’
          20180621-195624 SVNLogEntry=795111
          20180621-195624 svn:log=xxxx trigger build
          20180621-195624 svn:author=dietmar.scheidl
          20180621-195624 svn:date=2018-06-21T17:55:13.526105Z
          20180621-195624 M /trunk/product/...
          [Pipeline] }
          [Pipeline] // node
          [Pipeline] }
          [Pipeline] // stage
          [Pipeline] }
          [Pipeline] // timestamps
          [Pipeline] emailext
          messageContentType = text/html; charset=UTF-8
          Adding recipients from project recipient list
          Adding ....
          Adding ....
          Adding recipients from trigger recipient list
          Successfully created MimeMessage
          Sending email to: ....
          [Pipeline] End of Pipeline
          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:70)
              at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:57)
              at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:760)
              at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:352)
              at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:340)
              at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:897)
              at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:363)
              at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:353)
              at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.logImpl(DAVRepository.java:1003)
              at org.tmatesoft.svn.core.io.SVNRepository.log(SVNRepository.java:1041)
              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:1239)
              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:190)
          Caused: hudson.util.IOException2: revision check failed on https://xxx/trunk/product
              at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:204)
              at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:124)
              at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:757)
              at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:898)
              at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:113)
              at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:85)
              at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:75)
              at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47)
              at hudson.security.ACL.impersonate(ACL.java:290)
              at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44)
              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:1149)
              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
              at java.lang.Thread.run(Thread.java:748)
          Finished: FAILURE

          Dietmar Scheidl added a comment - - edited Sadly happend again ... I only added a space to one of the files and commited that change ... the log recorded the change but it seems creating the changelog.xml failed somehow. Started by an SCM change Opening connection to https://xxx/ Checking out svn https://xxx/trunk/product/pipeline/build into /var/lib/jenkins/workspace/_trunk_product_pipeline_build-...@script to read Jenkinsfile Updating https://xxx/trunk/product/pipeline/build@795111 at revision 795111 Using sole credentials ******/****** (******) in realm ‘<https://xxx:443> Subversion Software Development repository’ At revision 795111 ... No changes for https://xxx/trunk/product/pipeline/build since the previous build Running in Durability level: MAX_SURVIVABILITY [Pipeline] properties [Pipeline] library Loading library pipeline-library@trunk/product/pipeline/library Opening connection to https://xxx/ Updating https://xxx/trunk/product/pipeline/library@795111 at revision 795111 Using sole credentials ******/****** (******) in realm ‘<https://xxx:443> Subversion Software Development repository’ At revision 795111 No changes for https://xxx/trunk/product/pipeline/library since the previous build [Pipeline] timestamps [Pipeline] { [Pipeline] stage [Pipeline] { (init) [Pipeline] node 20180621-195613 Agent k8s-pipeline-mnj1s is provisioned from template Kubernetes Pod Template 20180621-195613 Agent specification [Kubernetes Pod Template] (pipeline): 20180621-195613 * [jnlp] docker-registry/library/someimage:latest(resourceRequestCpu: , resourceRequestMemory: , resourceLimitCpu: , resourceLimitMemory: ) 20180621-195613 20180621-195613 Running on k8s-pipeline-mnj1s in /home/jenkins/workspace/_trunk_product_pipeline_build-... [Pipeline] { [Pipeline] checkout 20180621-195613 Updating https://xxx/trunk/common at revision '2018-06-21T17:56:10.538 +0000' 20180621-195613 Using sole credentials ******/****** (******) in realm ‘<https://xxx:443> Subversion Software Development repository’ 20180621-195613 At revision 795111 20180621-195613 20180621-195614 Updating https://xxx/trunk/product at revision '2018-06-21T17:56:10.538 +0000' 20180621-195614 Using sole credentials ******/****** (******) in realm ‘<https://xxx:443> Subversion Software Development repository’ 20180621-195615 U ... 20180621-195623 At revision 795111 20180621-195623 20180621-195624 No changes for https://xxx/trunk/common since the previous build 20180621-195624 Computing changelog of https://xxx/trunk/product from 795111 to 795111 20180621-195624 Using sole credentials ******/****** (******) in realm ‘<https://xxx:443> Subversion Software Development repository’ 20180621-195624 SVNLogEntry=795111 20180621-195624 svn:log=xxxx trigger build 20180621-195624 svn:author=dietmar.scheidl 20180621-195624 svn:date=2018-06-21T17:55:13.526105Z 20180621-195624 M /trunk/product/... [Pipeline] } [Pipeline] // node [Pipeline] } [Pipeline] // stage [Pipeline] } [Pipeline] // timestamps [Pipeline] emailext messageContentType = text/html; charset=UTF-8 Adding recipients from project recipient list Adding .... Adding .... Adding recipients from trigger recipient list Successfully created MimeMessage Sending email to: .... [Pipeline] End of Pipeline 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:70) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.error(SVNErrorManager.java:57) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:760) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:352) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:340) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:897) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:363) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:353) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.logImpl(DAVRepository.java:1003) at org.tmatesoft.svn.core.io.SVNRepository.log(SVNRepository.java:1041) 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:1239) 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:190) Caused: hudson.util.IOException2: revision check failed on https://xxx/trunk/product at hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:204) at hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:124) at hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:757) at hudson.scm.SubversionSCM.checkout(SubversionSCM.java:898) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:113) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:85) at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:75) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1$1.call(AbstractSynchronousNonBlockingStepExecution.java:47) at hudson.security.ACL.impersonate(ACL.java:290) at org.jenkinsci.plugins.workflow.steps.AbstractSynchronousNonBlockingStepExecution$1.run(AbstractSynchronousNonBlockingStepExecution.java:44) 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:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) Finished: FAILURE

          The "funny" thing is, this happend yesterday right after restart of jenkins. But after some time the failure is gone and it works normally.

          Dietmar Scheidl added a comment - The "funny" thing is, this happend yesterday right after restart of jenkins. But after some time the failure is gone and it works normally.

          Shannon Kerr added a comment - - edited

          We just encountered this.

          • Jenkins via docker: 2.138.1
          • Subversion plugin: 2.11.1
          • svn: direct
          • No externals
          • No different credentials

          So far, just one build.  I recently added the sleep per JENKINS-34313 to avoid the changelog11.xml parsing failure, as we were hitting that issue more and more often.

           

           

          Shannon Kerr added a comment - - edited We just encountered this. Jenkins via docker: 2.138.1 Subversion plugin: 2.11.1 svn: direct No externals No different credentials So far, just one build.  I recently added the sleep per  JENKINS-34313 to avoid the changelog11.xml parsing failure, as we were hitting that issue more and more often.    

          Vassilena Treneva added a comment - - edited

          We are seeing quite often this (or maybe other?) problem.

          Jenkins ver. 2.140
          Subversion Plug-in 2.12.1

          checkout([
          $class: 'SubversionSCM',
          additionalCredentials: [[
          credentialsId: 'TEST_USER',
          realm: 'http://XXXX:80/'
          ]],
          excludedCommitMessages: '',
          excludedRegions: '',
          excludedRevprop: '',
          excludedUsers: '',
          filterChangelog: false,
          ignoreDirPropChanges: false,
          includedRegions: '',
          locations: [[
          cancelProcessOnExternalsFail: true,
          credentialsId: 'TEST_USER',
          depthOption: 'infinity',
          ignoreExternalsOption: true,
          local: '.',
          remote: "${svnBranch}@${buildNumber}"
          ]],
          quietOperation: false,
          workspaceUpdater: [$class: 'CheckoutUpdater']
          ])

          11:48:15 Caught Throwable. Retrying operation...
          [Pipeline] echo
          11:48:15 Exception type: class hudson.util.IOException2
          [Pipeline] echo
          11:48:15 Exception message: revision check failed on <REPO_URL>
          [Pipeline] echo

          Stacktrace:

          hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:204)
          hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:124)
          hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:757)
          hudson.scm.SubversionSCM.checkout(SubversionSCM.java:898)
          org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120)
          org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90)
          org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77)
          org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50)
          hudson.security.ACL.impersonate(ACL.java:290)
          org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47)
          java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
          java.util.concurrent.FutureTask.run(FutureTask.java:266)
          java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
          java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
          java.lang.Thread.run(Thread.java:748)

           

          Vassilena Treneva added a comment - - edited We are seeing quite often this (or maybe other?) problem. Jenkins ver. 2.140 Subversion Plug-in 2.12.1 checkout([ $class: 'SubversionSCM', additionalCredentials: [[ credentialsId: 'TEST_USER', realm: 'http://XXXX:80/' ]], excludedCommitMessages: '', excludedRegions: '', excludedRevprop: '', excludedUsers: '', filterChangelog: false, ignoreDirPropChanges: false, includedRegions: '', locations: [[ cancelProcessOnExternalsFail: true, credentialsId: 'TEST_USER', depthOption: 'infinity', ignoreExternalsOption: true, local: '.', remote: "${svnBranch}@${buildNumber}" ]], quietOperation: false, workspaceUpdater: [$class: 'CheckoutUpdater'] ]) 11:48:15 Caught Throwable. Retrying operation... [Pipeline] echo 11:48:15 Exception type: class hudson.util.IOException2 [Pipeline] echo 11:48:15 Exception message: revision check failed on <REPO_URL> [Pipeline] echo Stacktrace: hudson.scm.SubversionChangeLogBuilder.buildModule(SubversionChangeLogBuilder.java:204) hudson.scm.SubversionChangeLogBuilder.run(SubversionChangeLogBuilder.java:124) hudson.scm.SubversionSCM.calcChangeLog(SubversionSCM.java:757) hudson.scm.SubversionSCM.checkout(SubversionSCM.java:898) org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:120) org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:90) org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:77) org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1$1.call(SynchronousNonBlockingStepExecution.java:50) hudson.security.ACL.impersonate(ACL.java:290) org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution$1.run(SynchronousNonBlockingStepExecution.java:47) java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) java.util.concurrent.FutureTask.run(FutureTask.java:266) java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) java.lang.Thread.run(Thread.java:748)  

            Unassigned Unassigned
            scddev Dietmar Scheidl
            Votes:
            4 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: