[JIRA] [subversion-plugin] (JENKINS-26425) Jenkins subversion authentication error

2015-01-14 Thread siddharth.ku...@landg.com (JIRA)












































 
siddharth kumar
 edited a comment on  JENKINS-26425


Jenkins subversion authentication error
















Daniel - All I want to know is why after LINUX Kernel PATCH upgrade its not working.



























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







-- 
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] [subversion-plugin] (JENKINS-26425) Jenkins subversion authentication error

2015-01-14 Thread siddharth.ku...@landg.com (JIRA)














































siddharth kumar
 commented on  JENKINS-26425


Jenkins subversion authentication error















Thanks Daniel.In that case I will check this with latest version



























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







-- 
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] [subversion-plugin] (JENKINS-26425) Jenkins subversion authentication error

2015-01-14 Thread siddharth.ku...@landg.com (JIRA)














































siddharth kumar
 commented on  JENKINS-26425


Jenkins subversion authentication error















Daniel -I didn't expect this language from you. All I want to know is why after LINUX Kernel PATCH upgrade its not working.What has went wrong?you should n't run away by saying this used to happen with old version of Jenkins and Subversion plugin.Tell me the root cause



























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







-- 
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] [subversion-plugin] (JENKINS-26425) Jenkins subversion authentication error

2015-01-14 Thread dan...@beckweb.net (JIRA)














































Daniel Beck
 commented on  JENKINS-26425


Jenkins subversion authentication error















This is an issue tracker, not a support site. So when you're reporting an issue here, it needs to be relevant to the current state of the project. Otherwise developers spend effort trying to reproduce a problem (in this case that's quite a bit of effort, if possible at all given how little information you provide) that may have been fixed long ago. Subversion plugin 1.45 is obsolete since May 2013, Jenkins 1.534 unsupported since October 2014.

On the other hand, it shouldn't take you more than ten minutes to launch a current version of Jenkins on the affected machine (different port and Jenkins home of course), update SVN plugin to the current release, and confirm it still occurs with new versions in your environment. It makes the devs' job much easier without being a significant burden for you.

I'm not the only one with that view, see JENKINS-26011 for a similar example (it may also provide a hint as to what may be the problem here).

To get assistance in resolving this problem, rather than report an issue, email the jenkinsci-users list, or ask in #jenkins on Freenode. Alternatively, contact one of the commercial Jenkins support vendors, such as Cloudbees, about a Jenkins support contract.



























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







-- 
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] [subversion-plugin] (JENKINS-26425) Jenkins subversion authentication error

2015-01-14 Thread dan...@beckweb.net (JIRA)












































 
Daniel Beck
 edited a comment on  JENKINS-26425


Jenkins subversion authentication error
















This is an issue tracker, not a support site. So when you're reporting an issue here, it needs to be relevant to the current state of the project. Otherwise developers spend effort trying to reproduce a problem (in this case that's quite a bit of effort, if possible at all given how little information you provide) that may have been fixed long ago. Subversion plugin 1.45 is obsolete since May 2013, Jenkins 1.534 unsupported since October 2013.

On the other hand, it shouldn't take you more than ten minutes to launch a current version of Jenkins on the affected machine (different port and Jenkins home of course), update SVN plugin to the current release, and confirm it still occurs with new versions in your environment. It makes the devs' job much easier without being a significant burden for you.

I'm not the only one with that view, see JENKINS-26011 for a similar example (it may also provide a hint as to what may be the problem here).

To get assistance in resolving this problem, rather than report an issue, email the jenkinsci-users list, or ask in #jenkins on Freenode. Alternatively, contact one of the commercial Jenkins support vendors, such as Cloudbees, about a Jenkins support contract.



























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







-- 
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] [subversion-plugin] (JENKINS-26425) Jenkins subversion authentication error

2015-01-14 Thread siddharth.ku...@landg.com (JIRA)














































siddharth kumar
 created  JENKINS-26425


Jenkins subversion authentication error















Issue Type:


Bug



Assignee:


Unassigned


Components:


subversion-plugin



Created:


14/Jan/15 12:34 PM



Description:


Hi All,

I am running Jenkins in Apache tomcat server and after kernel upgrade to PATCH 3.I am getting the below error Please help

INFO: Failed to access subversion repository https://SVNREPO/TestPMD
Throwable occurred: org.tmatesoft.svn.core.SVNException: svn: E175002: OPTIONS /TestPMD failed
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:379)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:364)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:352)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:708)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:628)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:103)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1018)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.testConnection(DAVRepository.java:99)
at hudson.scm.SubversionSCM$DescriptorImpl.checkRepositoryPath(SubversionSCM.java:2038)
at hudson.scm.SubversionSCM$DescriptorImpl.doCheckRemote(SubversionSCM.java:1972)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java:611)
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:297)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:160)
at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:95)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:685)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:799)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:239)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:685)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:799)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:239)
at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:685)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:799)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:587)
at org.kohsuke.stapler.Stapler.service(Stapler.java:218)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:723)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
at 

[JIRA] [subversion-plugin] (JENKINS-26425) Jenkins subversion authentication error

2015-01-14 Thread dan...@beckweb.net (JIRA)















































Daniel Beck
 resolved  JENKINS-26425 as Cannot Reproduce


Jenkins subversion authentication error
















As I already wrote in JENKINS-26401, this needs to happen with current versions of Jenkins and Subversion plugin to be relevant. You're really outdated with both of them.

Besides, would you please stop creating the same crap issue over and over? This is the third copy, after JENKINS-26401 and JENKINS-26400.





Change By:


Daniel Beck
(14/Jan/15 12:59 PM)




Status:


Open
Resolved





Resolution:


CannotReproduce



























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







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