[JIRA] (JENKINS-53539) org.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled

2019-03-01 Thread kya...@blizzard.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Yates commented on  JENKINS-53539  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: org.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled   
 

  
 
 
 
 

 
 This continues to occur.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53539) org.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled

2018-12-05 Thread kya...@blizzard.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Yates updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53539  
 
 
  org.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled   
 

  
 
 
 
 

 
Change By: 
 Keith Yates  
 
 
Priority: 
 Major Critical  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53539) org.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled

2018-12-05 Thread kya...@blizzard.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Yates commented on  JENKINS-53539  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: org.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled   
 

  
 
 
 
 

 
 Adding additional information as it appears to most frequently occur with 'empty' depth checkouts.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53539) org.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled

2018-12-05 Thread kya...@blizzard.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Yates updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53539  
 
 
  org.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled   
 

  
 
 
 
 

 
Change By: 
 Keith Yates  
 

  
 
 
 
 

 
 {code:java}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:910) 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 {redacted} 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(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at 

[JIRA] (JENKINS-53539) org.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled

2018-12-05 Thread kya...@blizzard.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Yates updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53539  
 
 
  org.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled   
 

  
 
 
 
 

 
Change By: 
 Keith Yates  
 

  
 
 
 
 

 
 {code:java}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:910) 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 {redacted} 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(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at 

[JIRA] (JENKINS-53539) org.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled

2018-11-07 Thread kya...@blizzard.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Yates commented on  JENKINS-53539  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: org.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled   
 

  
 
 
 
 

 
 This continues to occur.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2018-09-12 Thread kya...@blizzard.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Yates commented on  JENKINS-32167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
 Similar to this issues JENKINS-37642  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-53539) org.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled

2018-09-12 Thread kya...@blizzard.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Yates updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53539  
 
 
  org.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled   
 

  
 
 
 
 

 
Change By: 
 Keith Yates  
 

  
 
 
 
 

 
 {code:java} 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:910) 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  { redacted} 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(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) 

[JIRA] (JENKINS-53539) org.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled

2018-09-12 Thread kya...@blizzard.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Yates updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53539  
 
 
  org.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled   
 

  
 
 
 
 

 
Change By: 
 Keith Yates  
 

  
 
 
 
 

 
 {code:java} 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:910) 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 { redacted} 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(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) 

[JIRA] (JENKINS-53539) org.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled

2018-09-12 Thread kya...@blizzard.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Yates updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53539  
 
 
  org.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled   
 

  
 
 
 
 

 
Change By: 
 Keith Yates  
 

  
 
 
 
 

 
 {code:java}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:910) 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  http://fenriscode-repository/branches/trunk  {redacted}  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(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at 

[JIRA] (JENKINS-53539) org.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled

2018-09-12 Thread kya...@blizzard.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Yates created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-53539  
 
 
  org.tmatesoft.svn.core.SVNException: svn: E130003: Parser configuration problem: namespace reporting is not enabled   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Ivan Fernandez Calvo  
 
 
Components: 
 subversion-plugin  
 
 
Created: 
 2018-09-12 21:52  
 
 
Priority: 
  Major  
 
 
Reporter: 
 Keith Yates  
 

  
 
 
 
 

 
 

 

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:910)
	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 

[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2018-09-12 Thread kya...@blizzard.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Yates updated  JENKINS-32167  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Nevermind the description doesn't match my issue.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-32167  
 
 
  ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
Change By: 
 Keith Yates  
 
 
Status: 
 Reopened Fixed but Unreleased  
 
 
Resolution: 
 Fixed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2018-09-12 Thread kya...@blizzard.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Yates reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 I'm experiencing this on 2.11.1 I saw a related ticket that state it might be related to xUnit plugin also being installed if that helps.  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-32167  
 
 
  ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
Change By: 
 Keith Yates  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Resolved Reopened  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-32167) ISVNAuthentication provider did not provide credentials

2018-09-12 Thread kya...@blizzard.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Keith Yates updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-32167  
 
 
  ISVNAuthentication provider did not provide credentials   
 

  
 
 
 
 

 
Change By: 
 Keith Yates  
 
 
Comment: 
 I'm experiencing this on 2.11.1I saw a related ticket that state it might be related to xUnit plugin also being installed if that helps.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)  
 

  
 

   





-- 
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.