[JIRA] (JENKINS-10095) No initial checkin to svn

[d...@doodle.com (JIRA)]

David Gubler commented on JENKINS-10095 No initial checkin to svn I'm having the same problem. I think the issue is that while a certificate is configured in jenkins, it is not used by the plugin for the initial checkout. That's what I can see in the apache log: dev.doodle.com:443 188.92.145.101 - jenkins [19/Jun/2012:15:13:16 +0200] "OPTIONS /svn/gmen_internal/Engineering/Jenkins HTTP/1.1" 200 5993 "-" "SVN/1.6.6 SVNKit/1.3.2 (http://svnkit.com/) rSNAPSHOT" dev.doodle.com:443 188.92.145.101 - jenkins [19/Jun/2012:15:13:16 +0200] "OPTIONS /svn/gmen_internal/Engineering/Jenkins HTTP/1.1" 200 5993 "-" "SVN/1.6.6 SVNKit/1.3.2 (http://svnkit.com/) rSNAPSHOT" dev.doodle.com:443 188.92.145.101 - - [19/Jun/2012:15:13:39 +0200] "OPTIONS /svn/gmen_internal/Engineering/Jenkins HTTP/1.1" 403 5880 "-" "SVN/1.6.6 SVNKit/1.3.2 (http://svnkit.com/) rSNAPSHOT" dev.doodle.com:443 188.92.145.101 - - [19/Jun/2012:15:13:39 +0200] "OPTIONS /svn/gmen_internal/Engineering/Jenkins HTTP/1.1" 403 5880 "-" "SVN/1.6.6 SVNKit/1.3.2 (http://svnkit.com/) rSNAPSHOT" The first two lines happen when the input is validated (SCM sync configuration -> repostory url, insert url and click somewhere outside that input field), the second two lines happen when I click "apply". Thus the plugin "forgets" to authenticate using the certificate.

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