[JIRA] (JENKINS-16689) Jenkins complains about unauthorized SVN URL, but actually can access it, since IT IS authorized
Linards L commented on JENKINS-16689 Jenkins complains about unauthorized SVN URL, but actually can access it, since IT IS authorized Same here. Digget out all available logs in centos 5.6 but only trace found that svn auth through AD and LDAP was failing for some users. Fixed it by reverting to plugin version 1.44. I highly DO NOT RECOMMEND ANYONE to use version 1.45. 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/groups/opt_out.
[JIRA] (JENKINS-16689) Jenkins complains about unauthorized SVN URL, but actually can access it, since IT IS authorized
Linards L edited a comment on JENKINS-16689 Jenkins complains about unauthorized SVN URL, but actually can access it, since IT IS authorized Same here. Digget out all available logs in centos 5.6 but only trace found that svn auth through AD and LDAP was failing for some users. Fixed it by reverting to plugin version 1.44. I highly DO NOT RECOMMEND ANYONE to use version 1.45. Affecting Jenkins v1.494 @ jdk7 , win 2k8 r2 x64 sp1 datacenter. 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/groups/opt_out.
[JIRA] (JENKINS-16689) Jenkins complains about unauthorized SVN URL, but actually can access it, since IT IS authorized
Linards L edited a comment on JENKINS-16689 Jenkins complains about unauthorized SVN URL, but actually can access it, since IT IS authorized Same here. Digget out all available logs in centos 5.6 but only trace found that svn auth through AD and LDAP was failing for some users. Fixed it by reverting to plugin version 1.44. I highly DO NOT RECOMMEND ANYONE to use version 1.45. Affecting Jenkins v1.494 installation @ jdk7 , tomcat7 , win 2k8 r2 x64 sp1 datacenter. 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/groups/opt_out.
[JIRA] (JENKINS-16689) Jenkins complains about unauthorized SVN URL, but actually can access it, since IT IS authorized
Markus Karg created JENKINS-16689 Jenkins complains about unauthorized SVN URL, but actually can access it, since IT IS authorized Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: subversion Created: 07/Feb/13 6:40 PM Description: I want Jenkins to check SVN every few minutes for changes. So I give a URL to check: svn://host/some/path/project/trunk. Jenkins says, I am not authenticated. So I follow the link to authenticate. As I want to authenticate only once for all projects, I provide the URL svn://host, not the complete path to one particular project. I give user and password, and Jenkins says the authentication is OK. When I come back to the job config, Jenkins still warns that the authentication is not working. I ignore this and start a build, and look, Jenkins can access the SVN repository without problems. So I go back to the config, and still Jenkins says, it cannot authenticate... weird. Environment: Debian 6, Tomcat 6, Jenkins 1.500, Subversion Project: Jenkins Priority: Minor Reporter: Markus Karg 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/groups/opt_out.
